Opened 14 years ago
Last modified 12 years ago
#7005 confirmed Bug
Invalid <a> attribute causes CPU to run @100% on Chrome
Reported by: | Jeconais | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Core : Parser | Version: | 3.0 |
Keywords: | Cc: |
Description
This only happens in Chrome (Windows and Linux). IE and Firefox handle the situation properly.
Entering a malformed a tag, with an invalid and escaped attribute causes the page to freeze. Looking at the process manager, the tab in question was running at 100% cpu.
A combination of obscure bugs in my own code caused the invalid html that triggers this bug:
<a href="http://www.amazon.com/" store\"="">google</a>
In IE and Firefox, the invalid attribute "store" is completely removed.
To trigger:
http://nightly.ckeditor.com/6355/_samples/replacebyclass.html
Click "Source"
Paste above snippet
Click "Source" again
Not a huge bug, and obviously inputting correct html avoids this completely.
Change History (2)
comment:1 Changed 14 years ago by
Component: | General → Core : Parser |
---|---|
Status: | new → confirmed |
Version: | → 3.0 |
comment:2 Changed 12 years ago by
Now (4.1) all browsers behave like Opera. Link is parsed when setting data, but isn't correctly recognised and is encoded when getting data back.
Ticket confirmed
Additional info:Under Opera11, above link is parsed into: