[Bug 5753] parsing issues with legacy UAs


Rob Burns <rob@robburns.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #2 from Rob Burns <rob@robburns.com>  2008-06-14 09:46:30 ---
Because of the disparate ways UAs currently handle parsing of unknown elements,
the tree is constructed in a variety of ways. Also the content model supported
by the text/html serialization does not support the full HTML5 content model.

Imagine an editing UA with the tree


A user wants this serialized to text/html without loss of data so that it can
be pasted into an email application and sent to a recipient whose email UA only
supports text/html processing. Right now the data is simply lost. That's just
one example, but the problem/issue has wider implications.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 14 June 2008 09:47:05 UTC