177163 – Inline floating element sometimes rendered not-inline

Bug 177163 - Inline floating element sometimes rendered not-inline

Summary: Inline floating element sometimes rendered not-inline

Status:	RESOLVED CONFIGURATION CHANGED

Alias:	None

Product:	WebKit
Classification:	Unclassified
Component:	Layout and Rendering (show other bugs)
Version:	WebKit Local Build
Hardware:	Unspecified macOS 10.12

Importance:	P2 Normal
Assignee:	Nobody

URL:
Keywords:	BrowserCompat

Depends on:
Blocks:

Reported:	2017-09-19 10:09 PDT by Ben Dean
Modified:	2022-08-29 03:33 PDT (History)
CC List:	7 users (show)

See Also:

Attachments
test case (704 bytes, application/zip) 2017-09-19 10:10 PDT, Ben Dean	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ben Dean 2017-09-19 10:09:44 PDT

Webkit version: SVN Revision 222175 (also Safari 10.1.1)
Platform: Mac OSX 10.12.5

Inline floating element sometimes rendered not-inline

Steps to reproduce:

1. Unzip attached floatbug.zip
2. Open floatbug.html.

What is the expected behavior?
The elements ("First part" and "Second part") are displayed inline:
> First partSecond part

What went wrong?
They aren't:
> First part
> Second part

Interesting qualifications:
  - Executing document.body.innerHTML = document.body.innerHTML fixes the layout

  - The "First part" div gets its "float:left;" style from a <link>. Setting that css property
    via <style> element or inline style instead fixes the layout.

Comment 1 Ben Dean 2017-09-19 10:10:29 PDT

Created attachment 321206 [details]
test case

floatbug.html
floatbug.css

Comment 2 Ahmad Saleem 2022-08-29 03:33:05 PDT

I changed the test case in JSFiddle:

Link - https://jsfiddle.net/bou4eky5/

All browsers (Safari Technology Preview 152 on macOS 12.5.1, Chrome Canary 107 and Firefox Nightly 106) show it as "FirstpartSecond part" soo it is something along the lines fixed. So I am going to mark this as "RESOLVED CONFIGURATION CHANGED". Please reopen if anyone think it is not correct and upload new test case. Thanks!