Bug 263385

Summary:	[CSS 2.1 Conformance] [testcase] Border style conflict resolution: when border-width is the same, then ridge border-style wins over outset border-style
Product:	[Applications] konqueror	Reporter:	Gérard Talbot (no longer involved) <browserbugs2>
Component:	khtml	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kde
Priority:	NOR	Keywords:	testcase
Version:	4.7.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gérard Talbot (no longer involved) 2011-01-17 05:11:44 UTC

Version:           4.5.5 (using KDE 4.5.5) 
OS:                Linux

If 2 collapsing borders have the same 'border-width', then 'ridge' border-style wins over 'outset' border-style.

3 testcases:

a) 
http://test.csswg.org/suites/css2.1/20110111/html4/border-conflict-style-079.htm

b) 
http://test.csswg.org/suites/css2.1/20110111/html4/border-conflict-style-088.htm

c) 
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/ridge-wins-over-outset.html

CSS 2.1, section 17.6.2.1 Border conflict resolution states

"
If several have the same 'border-width' then styles are preferred in this order: 'double', 'solid', 'dashed', 'dotted', 'ridge', 'outset', 'groove', and the lowest: 'inset'.
"
http://www.w3.org/TR/CSS21/tables.html#border-conflict-resolution

Reproducible: Always

Steps to Reproduce:
Load 3 provided testcases

Actual Results:  
There is a red outset border in all 3 testcases

Expected Results:  
There should be a green ridge border in all 3 testcases.

Linux 2.6.35-24-generic-pae, i686 (32bits), Qt 4.7.0, Konqueror 4.5.5 here.

Comment 1 Allan Sandfeld 2011-03-27 18:15:18 UTC

Test is passed by firefox and opera, while webkitpart renders like khtml

Comment 2 Christoph Cullmann 2024-05-06 18:38:46 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