- From: ~:'' ありがとうございました。 <j.chetwynd@btinternet.com>
- Date: Mon, 30 Jul 2007 19:21:14 +0100
- To: Sergiu Dumitriu <sergiu.dumitriu@gmail.com>
- Cc: David Woolley <forums@david-woolley.me.uk>, www-style CSS <www-style@w3.org>
Sergiu, not sure how closely you are following this thread... unfortunately as discussed previously display:none has rather too large a remit for a user style sheet. that is it is difficult or more likely impossible to limit to a particular file type. this contrasts rather strongly with the case of img which specifically addresses a limited and specific range of file types. regards Jonathan Chetwynd On 30 Jul 2007, at 14:08, Sergiu Dumitriu wrote: ~:'' ありがとうございました。 wrote: > > David, > > you fail to address the query you highlight: > "Is there a good reason CSS does not cover this issue?" > is there a technical or other good reason beyond the historical > artefact is already stated. > > clearly many users might prefer to hide flash on a site by site > basis via there browser and quite likely a user style sheet. > You can hide flash by setting display:none on the object or embed element. But you cannot make only the sound inside the flash stop while the flash is a binary entity that does not understand CSS. > regards > > Jonathan Chetwynd > > > > On 30 Jul 2007, at 08:33, David Woolley wrote: > > > ~:'' ありがとうございました。 wrote: > >> this seems to be counter-intuitive, and a resolution by file type >> seems feasible or possibly even near-trivial. >> Is there a good reason CSS does not cover this issue? > > You are taking a view that represents a popular misconception that > web standard define the complete browser as a multimedia > presentation engine, and which leads to people asking about Flash > on www-html. > > In its original concept, HTML provided glue to ease the navigation > to resources in many different forms. Commercialisation has led to > something of a compound document concept and special sorts of links > that result in concurrent rendering of linked resources. However, > the fact still remains that, if you link to (embed, access with > object) resources rendered by third party products, you cannot > expect those third party products to fully integrate with the W3C > technologies in the core product. > > If HTML had been designed as a multimedia presentation tool, it > would be > different, but it might also not exist at all, because it would > have been in direct competition with tools better at doing that job > at the time it was invented. >
Received on Monday, 30 July 2007 18:25:16 UTC