Databases
StackOverflow2013
Postsdbo
POClosing <ul /> tags in contenteditable without inserting superfluous tags
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
    primarykey
    data
    text
    <p>Working with an unordered (or ordered) list in a contenteditable gives me a headache.</p> <p>Whenever I want to end editing the list by pressing <kbd>ENTER</kbd> twice the browser will close the <code>&lt;ul /&gt;</code> but inserts a <code>&lt;p /&gt;</code> (Firefox) or a <code>&lt;div /&gt;</code> (Chrome) tag that contains a <code>&lt;br /&gt;</code>.<br> <strong><a href="http://jsfiddle.net/JZ54G/8/" rel="nofollow noreferrer">Example here</a></strong></p> <p>My goal is to avoid that superfluous <code>&lt;p /&gt;</code> or <code>&lt;div /&gt;</code> and instead just close the <code>&lt;ul /&gt;</code>.<br> I have tried to modify <a href="https://stackoverflow.com/questions/2735672/how-to-change-behavior-of-contenteditable-blocks-after-on-enter-pressed-in-vario#3492423">Tim Down's</a> solution which will prevent the browser to insert <code>&lt;p /&gt;</code> or <code>&lt;div /&gt;</code> when pressing <kbd>ENTER</kbd> and instead inserts a clean <code>&lt;br /&gt;</code> tag.<br> <strong><a href="http://jsfiddle.net/4xyR2/1/" rel="nofollow noreferrer">Example here</a></strong></p> <p>Unfortunately though, when using that solution the <code>&lt;ul /&gt;</code> is never closed by the browser since only <code>&lt;br /&gt;</code> tags are inserted <em>inside</em> the <code>&lt;li /&gt;</code> item.</p> <p>So my question is: </p> <p><strong>How can I actively close the <code>&lt;ul /&gt;</code> by inserting a node or pasting html when pressing enter on the last empty <code>&lt;li /&gt;</code>?</strong></p> <p><strong><em>Update:</strong> In case the question is stll unclear: I am looking for a way to close the <code>&lt;ul /&gt;</code> without inserting <code>&lt;p /&gt;</code> or <code>&lt;div /&gt;</code> tags but just by inserting a good old plain <code>&lt;br /&gt;</code> instead</em></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USHoren
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwhat are you expecting? the `<ul>` IS "closed", by virtue of existing; there's no such thing as an unclosed `<ul>` in the DOM. when you press Enter twice, you ask to type _beyond_ the `<ul>`, and that blank line has to live somewhere, so the browser puts it in a `<p>`.
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. USEevee
    2. COMight be of some use: http://stackoverflow.com/questions/5602241/prevent-firefox-from-making-a-new-contenteditable-div-when-user-hits-return
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. USWilHall
    3. COi stumbled across this behaviour as well, but i observed that using FF6 there is no additional p-tag being entered - it happens in more recent FF versions only
      singulars
      1. POClosing <ul /> tags in contenteditable without inserting superfluous tags
      1. USThariama
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload