- From: Gérard Talbot <www-style@gtalbot.org>
- Date: Mon, 07 Nov 2016 16:12:04 -0500
- To: scratch65535@att.net
- Cc: Oriol Bugzilla <oriol-bugzilla@hotmail.com>, W3C www-style mailing list <www-style@w3.org>
Le 2016-11-07 09:12, scratch65535@att.net a écrit : > On Sat, 05 Nov 2016 17:47:51 -0400, you wrote: > >>> - there would be no privileged styling. Just as a function call >>> is equal to inline code, a class= would have the same precedence >>> as a style=. >> >> It does not right now. The correct usage for class attribute is to >> style >> a group of elements which have a meaning, some kind of logic inside >> the >> webpage designer. An inline style is (should be!) for an unique >> element. >> Therefore, an inline style should be more specific than a class. > > Unfortuately, graphic designers don't care about such > distinctions. They just get in the way. [snipped] Being a graphic designer is not enough to create a good (accessible, interoperable, efficient for download and rendering, easy to maintain, future-proof, etc) website or a good (accessible, interoperable, efficient for download and rendering, easy to maintain, future-proof, etc) webpage. You need to know how CSS works. And there are some good tutorials out there. > The software had enough intelligence to do the things that > computers are good at (regularity, repeatability, easy changes), > and didn't try to do those things computers are bad at > (creativity, psychology, design). A software is never as intelligent, smart as its users based on their knowledge and expertise and will never compensate lack of knowledge and expertise. Otherwise, just buy a pair of Nike shoes and Wilson brand tennis racquet and you should become as good as NBA basketball professional players and tennis professional players. Gérard
Received on Monday, 7 November 2016 21:12:40 UTC