Closed Bug 1880401 Opened 1 year ago Closed 1 year ago

inline border style is unreliably applied, sometimes only when the element is inspected

Categories

(Core :: CSS Parsing and Computation, defect)

Firefox 122
defect

Tracking

()

RESOLVED DUPLICATE of bug 1869771

People

(Reporter: fpahl, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

Visit the blog post at https://www.matuzo.at/blog/2022/100daysof-day50 (archived at http://web.archive.org/web/20240213111332/https://www.matuzo.at/blog/2022/100daysof-day50/; the bug manifests there, too) and scroll down to the last example of two "cards without image", right before "Further reading".

Actual results:

The right-hand box is sometimes loaded with a solid border, sometimes with a dotted border. It seems that the solid border is somewhat more likely when the load takes longer. When the box or one of its children is selected with the inspector's arrow tool in the developer tools, the solid border sometimes turns dotted.

Expected results:

The border should be dotted. The border style is set in an inline style element that seems to be correctly formed; other browsers display the border as dotted.

Sorry, it should have said "the last example of one card with image and one without". The bug manifests in the card without image.

Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core

I was able to reproduce this in Firefox Nightly 122.0a1 (2023-12-01), but not in newer builds e.g. 2024-01-01. While bisecting and looking at the potential fix-range, I found bug 1869771 which seems to be about this exact same issue on this exact same test page. :)

--> Marking as a duplicate.

Blocks: has-issues
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1869771
Resolution: --- → DUPLICATE

(The fix is included in Firefox 123 which is released on Feb 20th or thereabouts, in a few days from now.)

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