W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 14009] New: Consider treating linebreaks in <pre> specially for formatBlock etc.

From: <bugzilla@jessica.w3.org>
Date: Fri, 02 Sep 2011 22:03:03 +0000
To: public-webapps@w3.org
Message-ID: <bug-14009-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14009

           Summary: Consider treating linebreaks in <pre> specially for
                    formatBlock etc.
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTML Editing APIs
        AssignedTo: ayg@aryeh.name
        ReportedBy: ayg@aryeh.name
         QAContact: sideshowbarker+html-editing-api@gmail.com
                CC: mike@w3.org, public-webapps@w3.org


Consider this formatBlock testcase:

  ['<p>', '{<pre>&#10;foo&#10;&#10;bar&#10;</pre>}'],

Chrome 15 dev produces

 <p>&#10;foo<br>&#10;bar</p>

while the spec, IE9, and Firefox 8.0a2 produce

  <p>{foo&#10;bar&#10;&#10;}</p>

Opera 11.50 is similar to IE/Firefox.  Should we special-case this the way
WebKit does, or not?  WebKit probably better matches user expectations, but it
might be annoying to handle.  If we do special-case it, we likely want to just
replace all the newlines by <br> right before any time when we might plausibly
change the tag name.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 2 September 2011 22:03:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT