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

Steps to reproduce:

Go to this link, the notation (SVG based) should show all the staff lines and note stems.

http://michaeleskin.com/abctools/abctools.html?lzw=BoLgBAjAUAKuMAsCmYDSSDOCoCVwCkBLAcygFlwA2AegA4oAZcCOqVcAcQFsBDAKygARAD6cAghzAcxAITDCwssYpkATeWCSr1xbRq1zVM5cKjTJ0uQqUr1CrTqPyIijgDEpAJkFgQwz64eHJ5iwqaiYDKehmr6xChGJpGyYEaS1sauJlBRkamx9vH5dmDEAGbEYDzEPM5gAEbElcQhvv4NTaXe8gC6QA&format=noten&ssp=10&pdf=one&pn=none&fp=yes&name=kesh

This used to work perfectly on Mac before the version 112 update on April 12, 2023.

Actual results:

Staff lines and note stems are not being rendered.

Expected results:

Staff lines and note stems should be visible, and were previous to the 112 update.

The Bugbug bot thinks this bug should belong to the 'Core::SVG' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Maybe you could use https://mozilla.github.io/mozregression/ to find an exact regression range.

This is my first time reporting a bug on Firefox, so can't be of much help with the regression range, I just build the music transcription tool, which started showing this issue for the first time with this morning's Mac update to version 112.

My copy of Firefox on Mac auto-updates, so which ever version was before 112 didn't have this issue, while 112 does. I'm not familiar with the regression tool, can someone please run this and enter the report? Worked fine on April 11th, 2023, and started failing with the 112 version installed by an auto-update on April 12th, 2023.

Now seeing other sites effected by the same bug:

https://thesession.org/tunes/693#setting46746

Notice the random thick and thin lines for the note stems and staff lines. That's new behavior with version 112.

Another site showing the same issue, SVG vertical note stems and staff lines not showing up on Firefox 112, fine before:

https://editor.drawthedots.com/?t=X%3A%201%0AT%3A%20The%20Kesh%0AR%3A%20Jig%0AM%3A%206%2F8%0AL%3A%201%2F8%0AK%3A%20Gmaj%0AD%7C%3A%20GAG%20GAB%20%7C%20ABA%20ABd%20%7C%20edd%20gdd%20%7C%20edB%20dBA%20%7C%0AGAG%20GAB%20%7C%20ABA%20ABd%20%7C%20edd%20gdB%20%7C1%20AGF%20G2D%20%3A%7C2%20AGF%20G2A%7C%7C%0A%7C%3A%20B2B%20dBd%20%7C%20ege%20dBA%20%7C%20BAB%20dBG%20%7C%20ABA%20AGA%20%7C%0AB2%20B%20dBd%20%7C%20ege%20dBd%20%7C%20gfg%20aga%20%7C1%20bgg%20g2A%20%3A%7C2%20bgg%20g2D%20%7C%5D

And yet another:

https://abc.rectanglered.com/

Probably bug 1780191 will fix this.

Bisected to bug 1811978.

Set release status flags based on info from the regressing bug 1811978

:gw, since you are the author of the regressor, bug 1811978, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

Confirmed, bug 1780191 will fix this. I will push it shortly and likely request uplift to beta.

I arrived at the same regressor. I did want to point out for the STR, I think the screen resolution matters.
I can reproduce the issue on 1920x1080 on my mac 13.3.1 in 112.0 but the same window moved over to a 1440x900 resolution works just fine.

I just tried my original reported issue it on a reduced resolution monitor at 1600x1000 and am seeing the same issue on Firefox 112.

http://michaeleskin.com/abctools/abctools.html?lzw=BoLgBAjAUAKuMAsCmYDSSDOCoCVwCkBLAcygFlwA2AegA4oAZcCOqVcAcQFsBDAKygARAD6cAghzAcxAITDCwssYpkATeWCSr1xbRq1zVM5cKjTJ0uQqUr1CrTqPyIijgDEpAJkFgQwz64eHJ5iwqaiYDKehmr6xChGJpGyYEaS1sauJlBRkamx9vH5dmDEAGbEYDzEPM5gAEbElcQhvv4NTaXe8gC6QA&format=noten&ssp=10&pdf=one&pn=none&fp=yes&name=kesh

Same for 1280x800 on Firefox 112, still missing staff lines and note stems.

(In reply to Timothy Nikkel (:tnikkel) from comment #11)

Confirmed, bug 1780191 will fix this. I will push it shortly and likely request uplift to beta.

Let's mark this as a duplicate then. We can reopen if bug 1780191 doesn't fix this.

(In reply to seisiuneer from comment #13)

I just tried my original reported issue it on a reduced resolution monitor at 1600x1000 and am seeing the same issue on Firefox 112.

Thanks - I think that's consistent with our understanding of what's going on; i.e. that this was introduced by the patch for bug 1811978 which landed as part of the Firefox 112 cycle.