Bug 241157

Summary: Konqueror ignores <col> width, if col contains span attribute
Product: [Applications] konqueror Reporter: Frank Steinmetzger <dev+kde>
Component: khtml parsingAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: 4.4.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Example file showing tables with different <col> setup

Description Frank Steinmetzger 2010-06-09 00:46:48 UTC
Created attachment 47822 [details]
Example file showing tables with different <col> setup

Version:           4.4.0 (using KDE 4.4.3) 
OS:                Linux

I already thought Konqueror would ignore <col width=…> alltogether, but just discovered that it works if I include the DTD in the doctype (in my case 4.01 Transitional).

Now that I got that right, I did however encounter a flaw afterwards:
Konqueror again ignores the width I set in a <col>, if I add a span attribute in order to give the following col(s) the same width.

Reproducible: Always

Steps to Reproduce:
Use a table colgroup with a col that has a span attribute.

Actual Results:  
Konqueror ignores col width=…, if the col also contains span=… (and renders the table as if no colgroup statement was there at all).

Expected Results:  
If <col width="x" span="y"> is used, the col and y-1 next cols should receive a width setting of x.
Comment 1 Andrew Crouthamel 2018-11-02 23:01:29 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 05:35:46 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-13 02:53:41 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-28 05:25:28 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-12 05:18:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!