Bug 198099 - [CSS 2.1 Conformance] Parsing of an escaped character next to property value
Summary: [CSS 2.1 Conformance] Parsing of an escaped character next to property value
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml parsing (show other bugs)
Version: 4.7.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL: http://www.gtalbot.org/BrowserBugsSec...
Keywords: reproducible, testcase, triaged
Depends on:
Blocks:
 
Reported: 2009-06-28 00:00 UTC by Gérard Talbot (no longer involved)
Modified: 2024-05-06 20:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gérard Talbot (no longer involved) 2009-06-28 00:00:09 UTC 
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Testcase from Gabriele Romanato
--------

http://test.csswg.org/source/CSS2.1-test-suite/incoming/gabriele/basic/sec4/char12.html

Relevant code involved:
----------------------

<style type="text/css">
p {color: green}
p {color: \20red}
</style>

<p>This text should be green, not red.</p>



"Backslash escapes, where allowed, are always considered to be part of an identifier or a string"
http://www.w3.org/TR/CSS21/syndata.html#characters

\20red is not the exact same identical string value of red (reserved color name identifier in CSS 2.1). So, the declaration
color: \20red
should be parsed as invalid (therefore rejected) and only p {color: green} should apply.

Internet Explorer 8, Firefox 3.0.11, Opera 9.64 and Safari 4 pass this test.

regards, Gérard
Comment 1 A. Spehr 2009-06-28 01:05:25 UTC 

*** This bug has been marked as a duplicate of bug 198086 ***
Comment 2 Gérard Talbot (no longer involved) 2009-06-28 01:24:25 UTC 
A. Spehr,

I am re-resolving this bug as a duplicate of bug 198096, not as 198086.

I intentionally split the parsing bugs into 3 bug reports (198096, 198099 and 198103) because this is what is recommended when filing bugs. I don't mind them being regrouped under 1 bug report though.

regards, Gérard

*** This bug has been marked as a duplicate of bug 198096 ***
Comment 3 A. Spehr 2009-06-28 12:35:42 UTC 
Sorry, you are right. From where I was reading it looked like you had just hit "submit" a few too many times. :} I reopened and moved around labels to make it easier to read the subject.
Comment 4 Gérard Talbot (no longer involved) 2009-09-30 07:03:45 UTC 

http://test.csswg.org/source/contributors/gabriele/incoming/basic/sec4/char12.html
Comment 5 Gérard Talbot (no longer involved) 2012-06-23 22:33:51 UTC 
URL field updated.

Gérard
Comment 6 Gérard Talbot (no longer involved) 2014-06-04 17:18:33 UTC 
Temporary url:
http://test.csswg.org/source/work-in-progress/gabriele/basic/sec4/char12.html
Comment 7 Gérard Talbot (no longer involved) 2014-06-12 17:00:31 UTC 
Permanent url:
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Bug198099-esacaping-character-property-value.html
Comment 8 Christoph Cullmann 2024-05-06 20:48:57 UTC 
Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann