Changes between Initial Version and Version 1 of Ticket #6187, comment 9


Ignore:
Timestamp:
Oct 31, 2013, 11:03:58 PM (6 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6187, comment 9

    initial v1  
    11Note that EnterKeyHandling with blockModeForEnter=P looks the same on IE, FF,and Chrome; they all have a fair amount of margin between the paragraphs.
    22
    3 So this ticket wasn't about IE so much as about normalizing the behavior between browsers: about whether the enter key inserts a <br> or a new <p>.
     3So this ticket wasn't about IE so much as about normalizing the behavior between browsers: about whether the enter key inserts a <br> or a new <div> or <p>.
    44
    55I mention this all in relation to https://github.com/dojo/dijit/pull/6, in which case splitting up logical paragraphs with multiple <br> nodes is especially bad because you can't apply separate LTR and RTL formatting to each (logical) paragraph.   I.E. for text like:
     
    3737I checked out the [http://ckeditor.com/demo CKEditor demo] and their apparent default mode is blockModeForEnter=P, where shift-enter inserts a <br>.  Tested on Chrome and IE8.
    3838
    39 I'm tempted to normalize on that behavior.
     39I'm tempted to normalize on that behavior, or on using DIV.   I like P in general, but DIV is better for users that don't know about shift-enter (or are on an iPad) and want to have conceptual newlines in their document.