Mailing list search service

1. Re: [css-inline] Summary of drop-caps/initial-letters discussion (score: 11) (4,376 bytes)
Author: Liam R E Quin <liam@w3.org>, Date: Tue, 20 May 2014 06:06:44 -0400 List: Public/www-style
In-Reply-To: <CANz3_EZBvUy6cza_OMtfYqqriZ0UbBpsa9xm7422+y6q=z06_Q@mail.gmail.com> References: 1 2 3

Main issues seem to be 1. identifying which text to make large - e.g. Hebrew and Arabic texts sometimes use "drop words", suggesting use of a :first-word selector, as Dave mentioned. Hindi uses a syl

2. Re: [css3-lists] Proposal: list item marker from the content of the li element (score: 11) (4,523 bytes)
Author: "Markus Ernst" <derernst@gmx.ch>, Date: Wed, 31 Mar 2010 09:56:40 +0200 List: Public/www-style
In-Reply-To: <dd0fbad1003301417r73c4031dq1bc47aabb28765ae@mail.gmail.com> References: 1 2

-- Original-Nachricht -- [...] The float property does not look really intuitive to me for this case, but if it provides the possibility to solve the use case at acceptable implementation cost, why n

3. Re: New pseudo-element? (score: 22) (2,089 bytes)
Author: "Neil Carson" <neil@liberate.com>, Date: Fri, 19 Apr 2002 12:29:35 -0400 (EDT) List: Public/www-style References: 1

Actually first-line is very hard to code :-) Things like first-letter or a first-word would likely be easier. Neil there were a :first-word pseudo-element, and it shouldn't be much more difficult to

4. Re: New pseudo-element? (score: 11) (1,813 bytes)
Author: "David Witchell" <dwitchell@sportcraftcars.com>, Date: Wed, 17 Apr 2002 14:29:18 -0400 (EDT) List: Public/www-style

Some of the web pages I am maintaining now could be made much smaller if there were a :first-word pseudo-element, and it shouldn't be much more difficult to code than :first-line. It doesn't look lik

5. Re: first-word pseudo-element (score: 171) (3,163 bytes)
Author: Jan Roland Eriksson <jrexon@newsguy.com>, Date: Sat, 19 May 2001 17:36:19 +0200 List: Public/www-style
In-Reply-To: <3B03D209.9070507@netscape.com> References: 1 2

Well, strictly speaking we don't have any "written word separators" in Latin based languages either. The specific (key) action of introducing a piece of white-space between words is probably an inven

6. Re: Location of pseudoelements (was: Re: first-word pseudo-element) (score: 171) (1,850 bytes)
Author: "Jonas Sicking" <sicking@bigfoot.com>, Date: Sat, 19 May 2001 15:47:58 +0200 List: Public/www-style References: 1

"Pseudo-elements may only appear once in the sequence of simple selectors that represents the subjects of the selector." / Jonas Sicking

7. Re: Location of pseudoelements (was: Re: first-word pseudo-element) (score: 171) (1,905 bytes)
Author: Ian Hickson <ian@hixie.ch>, Date: Sat, 19 May 2001 05:17:43 -0700 (Pacific Daylight Time) List: Public/www-style
In-Reply-To: <02c301c0e059$6ef5fd60$d1ee42d5@kermit>

It's illegal. :not() is only allowed to take one simple selector, and never pseudo-elements. Nope, because pseudo-elements (since CSS1) are only allowed at the end of the selector chain.

8. Location of pseudoelements (was: Re: first-word pseudo-element) (score: 171) (2,057 bytes)
Author: "Jonas Sicking" <sicking@bigfoot.com>, Date: Sat, 19 May 2001 13:47:05 +0200 List: Public/www-style References: 1 2 3 4

[snip] That section says that a pseudo element is only allowed once. This would allow selectors like this: div::first-line em { ... } elem:not{::first-line} Are they allowed? / Jonas Sicking

9. Re: first-word pseudo-element (score: 171) (3,317 bytes)
Author: Bjoern Hoehrmann <derhoermi@gmx.net>, Date: Sat, 19 May 2001 03:16:49 +0200 List: Public/www-style
In-Reply-To: <Pine.WNT.4.31.0105181639040.760-100000@HIXIE.netscape.com> References: 1 2

Generated content before the first line of the current user selection. I don't know whether I should put a smiley here... Why do you think so? If it is defined what each pseudo-element selects and th

10. Re: first-word pseudo-element (score: 171) (2,644 bytes)
Author: Ian Hickson <ian@hixie.ch>, Date: Fri, 18 May 2001 16:42:12 -0700 (Pacific Daylight Time) List: Public/www-style
In-Reply-To: <rfabgt09rbrj83t6oh2a6jtqjcsuf3hv56@4ax.com>

What does ...select? Basically, the reason for this restriction is that if you are allowed to combine them, you have to define exactly what every combination of pseudoelements means. Plus, it's an im

11. Re: first-word pseudo-element (score: 171) (2,275 bytes)
Author: Bjoern Hoehrmann <derhoermi@gmx.net>, Date: Sat, 19 May 2001 01:35:59 +0200 List: Public/www-style
In-Reply-To: <3B0593BD.AE74D52F@escape.com> References: 1 2 3 4

[...] Pseudo-elements may only appear once in the sequence of simple selectors that represents the subjects of the selector. [...] Why? [...] Pseudo-elements names are case-insensitive. [...] This st

12. Re: first-word pseudo-element (score: 181) (3,158 bytes)
Author: "Tantek Celik" <tantek@cs.stanford.edu>, Date: Fri, 18 May 2001 15:40:01 -0700 List: Public/www-style

I agree that "features that everybody can use" are a good goal. The difference is that I don't see that as a requirement, and not only that, my point is that sometimes trying to make a feature "unive

13. Re: first-word pseudo-element (score: 171) (3,317 bytes)
Author: fantasai <fantasai@escape.com>, Date: Fri, 18 May 2001 17:27:25 -0400 List: Public/www-style References: 1 2 3

See fantasai. "On nth-child, etc..", www-style. 2001-03-10 http://lists.w3.org/Archives/Public/www-style/2001Mar/0078.html and ensuing thread. Actually, I kinda like the :child(expr) syntax. :) It's

14. Re: first-word pseudo-element (score: 171) (2,605 bytes)
Author: Bjoern Hoehrmann <derhoermi@gmx.net>, Date: Fri, 18 May 2001 22:23:32 +0200 List: Public/www-style
In-Reply-To: <3B04D926.4040106@netscape.com> References: 1 2 3 4

properly marked up of cause. I don't want to see broken implementations, too. If the document is properly marked up, i.e. you set the (xml:)lang attribute, I don't see no problem here. The recent tex

15. RE: first-word pseudo-element (score: 181) (1,490 bytes)
Author: Sampo Syreeni <decoy@iki.fi>, Date: Fri, 18 May 2001 17:56:26 +0300 (EEST) List: Public/www-style
In-Reply-To: <A35E2040C17F0C48B941B8F4D0DF122908E4B0@ermhs.Athens.BrokerSystems.gr>

Sure. The character model is still that of Unicode's, even if the encoding varies. This is the same principle that is used with XML/HTML now. Sampo Syreeni, aka decoy, mailto:decoy@iki.fi, gsm: +358-

16. Re: first-word pseudo-element (score: 171) (2,683 bytes)
Author: glazman@netscape.com (Daniel Glazman), Date: Fri, 18 May 2001 16:53:04 +0200 List: Public/www-style References: 1

Are you saying that I should not be able to use a ruby box model with latin characters just because I like the effect it brings ? Or that I should not use grid layout because it is mainly made for id

17. Re: first-word pseudo-element (score: 181) (2,155 bytes)
Author: "Tantek Celik" <tantek@cs.stanford.edu>, Date: Fri, 18 May 2001 07:37:27 -0700 List: Public/www-style

I strongly disagree. It is reasonable to expect that different languages and writing systems will have different layout/typographic effects in common usage (yes, even before the web). Therefore, it i

18. RE: first-word pseudo-element (score: 192) (3,739 bytes)
Author: "Manos Batsis" <m.batsis@bsnet.gr>, Date: Fri, 18 May 2001 17:05:57 +0300 List: Public/www-style

Can't a hypothetical :first-word be used combined with a mandatory @charset ? lol... I guess css has no dtd... what about FO? Manos

19. Re: first-word pseudo-element (score: 171) (3,460 bytes)
Author: Sampo Syreeni <decoy@iki.fi>, Date: Fri, 18 May 2001 16:17:47 +0300 (EEST) List: Public/www-style
In-Reply-To: <Pine.WNT.4.31.0105180149070.760-100000@HIXIE.netscape.com>

Besides, even while most of the world seems to have writing systems that are a lot more difficult to handle than the ones based on the Latin alphabet, can this really be a reason to make it impossibl

20. Re: first-word pseudo-element (score: 171) (1,697 bytes)
Author: glazman@netscape.com (Daniel Glazman), Date: Fri, 18 May 2001 11:17:57 +0200 List: Public/www-style References: 1

Why ? text-transform is not applicable to some writing systems because these writing systems ignore the notion of lowercase and uppercase characters, not because the property is not applicable by con