Bug 235521

Summary: [CSS 2.1 Conformance] Position of a floated element in relation to a block previously (earlier) generated in the source.
Product: [Applications] konqueror Reporter: Gérard Talbot (no longer involved) <browserbugs2>
Component: khtmlAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal Keywords: testcase
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Gérard Talbot (no longer involved) 2010-04-27 05:21:18 UTC
Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

Testcase
--------

http://www.w3.org/Style/CSS/Test/CSS2.1/20100316/html4/floats-030.htm

Actual results in Konqueror 4.4.2
---------------------------------

The orange square is pushed outside the black bordered rectangle.
The orange square should be immediately below following the previously generated <div>Filler Text 1</div>.

Expected results
----------------

The orange square should be inside the black bordered rectangle.

Reference
---------
Rule 5 of precise rules that govern the behavior of floats states:
"
The outer top of a floating box may not be higher than the outer top of any block or floated box generated by an element earlier in the source document.
"
and rule 8 of those same rules states
"
A floating box must be placed as high as possible.
"
http://www.w3.org/TR/CSS21/visuren.html#floats

Notes
-----
Firefox 3.5.9, Firefox 3.6.3, IE8, Opera 10.10 and Safari 4.0.5 pass that testcase.

regards, Gérard
Comment 1 Andrew Crouthamel 2018-11-02 23:00:23 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:24:38 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-09 22:13:13 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-24 05:23:32 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-08 05:16:50 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!