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.

!important / @namespace

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan deanone

more options

Is it still necessary to use both !important and @namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul) inside userChrome?

Is it still necessary to use both ''!important'' and ''@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul)'' inside userChrome?

Keazen oplossing

I've been on a warpath against using @namespace for nearly four years. Ref. https://www.userchrome.org/adding-style-recipes-userchrome-css.html#namespaces

You need !important in many cases to overcome the sometimes unpredictable way that browsers apply the precedence rules of the CSS cascade: https://developer.mozilla.org/docs/Web/CSS/Cascade

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

more options

Keazen oplossing

I've been on a warpath against using @namespace for nearly four years. Ref. https://www.userchrome.org/adding-style-recipes-userchrome-css.html#namespaces

You need !important in many cases to overcome the sometimes unpredictable way that browsers apply the precedence rules of the CSS cascade: https://developer.mozilla.org/docs/Web/CSS/Cascade

more options

Thanks for that. I have been suspicious of @namespace for some time. I will omit it for the time being.