Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

::before and ::after css rules not showing in css inspector in developer edition

more options

when inspecting a webpage with devtools in the developer edition of FIrefox, the pseudo elements ::before and ::after show up OK in the HTML inspector, but when selected in the HTML inspector, the CSS rules for the pseudo elements do now show up in the CSS styles inspector. See attached screen shot.

Pseudo elements display just fine in google developer tools during inspetion.

when inspecting a webpage with devtools in the developer edition of FIrefox, the pseudo elements ::before and ::after show up OK in the HTML inspector, but when selected in the HTML inspector, the CSS rules for the pseudo elements do now show up in the CSS styles inspector. See attached screen shot. Pseudo elements display just fine in google developer tools during inspetion.
Keppele skermôfbyldingen

Keazen oplossing

Tuns out to be a bug when you have display:table in the ::before or ::after. See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1481192

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (3)

more options
more options

It still works in Firefox 61 (checking in this page, within #main-breadcrumbs), so perhaps it is regression in Developer Edition.

Could you try the DevTools forum to see whether this is a known issue?

https://discourse.mozilla.org/c/devtools

more options

Keazen oplossing

Tuns out to be a bug when you have display:table in the ::before or ::after. See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1481192