- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2019 22:43:54 +0000
- To: public-css-archive@w3.org
The reason it's surprising is: how is a component author, writing a reusable component meant to be included on a number of webpages written by other people, supposed to know that the @font-face name they chose collides with the @font-face that one of those other-website people chose? And on the other side, how is someone writing a website supposed to know that the font name they're using happens to *also* be used by one of the components on their page, written by someone else? The collision here is fully accidental on both people's parts, and can't be avoided except by naming your fonts with high-entropy random strings. That's clearly silly. ^_^ > You changed the definition of font foo, anything that inherited font foo should change. They *didn't* change the definition of font foo, tho. They *added a brand new font foo* within their shadow tree, and then inherited a completely unrelated font foo from their ancestor tree. The fact that the two have the same name is completely unintentional. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1995#issuecomment-495410864 using your GitHub account
Received on Thursday, 23 May 2019 22:43:56 UTC