Testcase attached. Basically I'm getting different interaction in a list between a select and a paragraph than I did in Firefox 3.

If you mean the position, the cause should be in here: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-06-10+15%3A00%3A00&enddate=2008-06-10+20%3A00%3A00 Maybe this changeset without bug: 5c30c5953d22 ?

Yeah, talking about position. This is actually a larger problem in our app, but when I started narrowing it down, this is the main difference that I found.

Yeah, that layout changed with bug 50630. Fx 3.1 + now behaves like WebKit and Opera - in Standards mode. Opera shows differences between Standard and Quirks mode. It is interesting to see that there differences between the browsers regarding the listmarker (with Opera 10alpha putting two listmarkers) I'll attach a screenshot next.

Testcase as seen in Standards mode Various browsers, I added the UA string in the testcase to distinguish them...

The change in float placement and thus the wrapping of the select around the float is an expected change from bug 50630. I'm a little surprised the bullet isn't moving along with the select, though.

Just verified this is still a problem. Looking at chrome, they put the bullet next to the select. We don't.

Tested this on the newest version of Nightly with the following specs: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 And there still seems to be a different behavior on the test case between the newest version of Nightly and Google Chrome. I've attached a test case that shows the difference. Google Chrome is on the left Nightly is on the right

Regarding the need info flag in Comment 7, I want to see if this remains a pertinent issue or if this bug should be closed.

Seems like the bullet position is the issue that needs fixing, and that hasn't changed.

Maybe related to bug 416732.

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.

This was fixed at some point. Woohoo!