[Webkit-unassigned] [Bug 54978] REGRESSION (r72489): TinyMCE not working in nightlies
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Mar 1 09:57:36 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=54978
Michael Saboff <msaboff at apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|webkit-unassigned at lists.web |msaboff at apple.com
|kit.org |
--- Comment #5 from Michael Saboff <msaboff at apple.com> 2011-03-01 09:57:35 PST ---
This bug is caused by improper handling of the regular expression /<(?:(?:!--([\w\W]*?)-->)|(?:!\[CDATA\[([\w\W]*?)\]\]>)|(?:!DOCTYPE([\w\W]*?)>)|(?:\?([^\s\/<>]+) ?([\w\W]*?)[?/]>)|(?:\/([^>]+)>)|(?:([^\s\/<>]+)\s*((?:[^"'>]+(?:(?:"[^"]*")|(?:'[^']*')|[^>]*))*)>))/
This regular expression appears to be looking for the contents inside <> HTML constructs.
The failing regular expression has been reduced to: /<((ABC>)|(\/([^>]+)>)|(([^>]+)>))/
with the (ABC>) added to make it fail.
The bug appears to be an issue with the "Beginning Characters" optimization added that seems to have a problem in the YARR interpreter. When the beginning characters optimization is disabled, the failing page operates correctly. The reason the (ABC>) was added to the above expression was that without that alternative, the beginning characters optimization worked correctly. It seems that the bug has to do with how far down the alternatives the begin characters setup code analyzes when creating the data for the optimization to use at runtime.
I will create a patch that will disable the beginning characters optimization and then create a new defect to address the beginning characters bug.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list