We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #13644, comment 4

Timestamp:: Aug 17, 2015, 3:00:36 PM (9 years ago)
Author:: Szymon Cofalik
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #13644, comment 4

-                      initial
+                      v1
 Here is a description why the bug happens:
 ) In htmlparser we use a pretty sophisticated regular expression that finds tag openings.
 ) When the algorithm finds `<style>` tag, it looks further into code, looking for closing tag, but it finds `<9 </style>` instead.
 ) Algorithm never finds closing tag for `<style>`.
+. In htmlparser we use a pretty sophisticated regular expression that finds tag openings.
+. When the algorithm finds `<style>` tag, it looks further into code, looking for closing tag, but it finds `<9 </style>` instead.
+. Algorithm never finds closing tag for `<style>`.
 If `<9` was a part of normal html code this won't be a bug but just invalid html code. Unfortunately, in `<style>` tag, in a comment, it is valid.