Difference between revisions of "User talk:Aichon"

From The Urban Dead Wiki
Jump to navigationJump to search
(→‎whyy: Making it link to the relevant section)
Line 93: Line 93:
Can you summarise in 25 words or less why new Mozilla no longer recognises moz-border codes? Changed to... webkit (I think it is)? {{User:DanceDanceRevolution/sig}} 16:00, 26 June 2012 (BST)
Can you summarise in 25 words or less why new Mozilla no longer recognises moz-border codes? Changed to... webkit (I think it is)? {{User:DanceDanceRevolution/sig}} 16:00, 26 June 2012 (BST)
:Yes, I can summarize it in 25 words or less. {{User:Aichon/Signature}} 16:13, 26 June 2012 (BST)
:Yes, I can summarize it in 25 words or less. {{User:Aichon/Signature}} 16:13, 26 June 2012 (BST)
::Anyway, I assume you're talking about moz-border-radius and the like. The reason why is that all of the prefix CSS properties (i.e. the ones starting with moz, webkit, or the like) are meant to eventually be replaced by a CSS standard equivalent, rather than staying proprietary forever. The border-radius property has been a standard for a long time, so [https://developer.mozilla.org/en/CSS/border-radius moz-border-radius support was finally phased out in Firefox 13]. Assuming you were using {{tl|xbrowsercss}} all along, this wouldn't be an issue for you, since that was designed specifically for the day that this situation arose. That's also why whenever you are using a CSS property with a prefix, you should also try to find the equivalent standard property and use it as well. {{User:Aichon/Signature}} 16:21, 26 June 2012 (BST)
::Anyway, I assume you're talking about moz-border-radius and the like. The reason why is that all of the prefix CSS properties (i.e. the ones starting with moz, webkit, or the like) are meant to eventually be replaced by a CSS standard equivalent, rather than staying proprietary forever. The border-radius property has been a standard for a long time, so [https://developer.mozilla.org/en/CSS/border-radius#Gecko_notes moz-border-radius support was finally phased out in Firefox 13]. Assuming you were using {{tl|xbrowsercss}} all along, this wouldn't be an issue for you, since that was designed specifically for the day that this situation arose. That's also why whenever you are using a CSS property with a prefix, you should also try to find the equivalent standard property and use it as well. {{User:Aichon/Signature}} 16:21, 26 June 2012 (BST)

Revision as of 15:22, 26 June 2012

Aichon:Talk
Aichon
ˈīˌkän :Talk