W3C home > Mailing lists > Public > www-style@w3.org > September 2012

Re: Discussing possibilities of a 'CSS-ignore' rule.

From: Ketan Singh <singh.ketan7@gmail.com>
Date: Sun, 23 Sep 2012 21:47:19 +0530
Message-ID: <CAH8sMT_TBa915f9nmmEiJmheZDWPDAb3c+1FcragiEXPAr451g@mail.gmail.com>
To: François REMY <fremycompany_pub@yahoo.fr>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: www-style@w3.org
Well I don't know the exact manner in which CSS is implemented by the
browsers. But I find it difficult to conceive how a browser CANNOT
ignore every other css property that is applied to an element, when
the 'css-ignore' property is specifically designed to make that
happen. If it cannot, I find the design of  the whole thing
inappropriate and unscalable, which shouldn't be the case with
something of this magnitude.
Given that the 'css-ignore' property is not something 'usual', and is
NOT meant to for the usual styling of elements, it obviously needs
special efforts to implement.
I find it difficult to believe that something 'is not possible to do',
especially at the software level, that too on a W3C mailing list!
If its not possible right now, we need to do something to make it
possible. That is the central point of engineering and innovation.
I'd love it if someone could help me learn how CSS is implemented by
the browsers, and in what manner does the W3C collaborate in its
actual implementation .
Maybe I could come up with an algorithm to do it, if I properly
understood the manner in which it is implemented.

Lets forget the 'use-case' for a while. All I want to say that the
'css-ignore' rule should get 'rid of styling', if the developer
deliberately wants to allow this. This can allow the browsers can do
things in their own way.
I see huge possibilities here. Maybe this will create an oppurtunity
for browsers or 3rd party bodies to create custom-css solutions for
elements that have the 'css-ignore' rule associated with it.
And given that the world is moving towards responsive design and
progressive enhancement, a strictly identical layout is not usually
expected. Hence, I see this property to be something that will be used
heavily in the future, and can provide something new for everyone; be
it developers, users or browsers designers. Do give it a serious
thought, we could be on the verge of something huge.




On Sun, Sep 23, 2012 at 6:15 PM, François REMY
<fremycompany_pub@yahoo.fr> wrote:
> I can’t help but repeat the arguments I already gave.
>
> The selectors matched by an element can’t depend on the result of the style
> applied on it, because that style depends on the selectors that matched it.
> At least, it can’t using pure CSS. The text color of a “<span>text</span>”
> with “span { color: blue; css-ignore: external }” is an undecidable problem
> and browsers, being software programs, can’t resolve undecidable problems.
>
> The use cases that one would like to solve with “css-ignore” on css-ignore
> should rely on some other mechanism instead, like IFRAMES and Web
> Components.
>
>
> From: Ketan Singh
> Sent: Sunday, September 23, 2012 12:18 PM
> To: Garrett Smith
> Cc: www-style@w3.org
> Subject: Re: Discussing possibilities of a 'CSS-ignore' rule.
> Well, my apologies for mentioning the use-case on the first place. I should
> have come to the point at once.
> About the 'potential blocking of popup' issue, the client have ordered the
> app for themselves, so most probably that's not going to happen, given that
> they requested for the 'whole experience'.
>
> I'm kind of new to mailing lists, I'm not here to debate on programming
> ideologies and best practices. I just want to share my thoughts on how we
> can take CSS forward, and I hope someone could spare a minute for the idea.
> I'd insist that you go through my last mail, and let me know your thoughts
> on it.
>
> Thanks
> Ketan
>
> On Sun, Sep 23, 2012 at 7:43 AM, Garrett Smith <dhtmlkitchen@gmail.com>
> wrote:
>>
>> On 9/21/12, Ketan Singh <singh.ketan7@gmail.com> wrote:
>> > Well, the project is basically an offline app, which is intended for a
>> > desktop environment. The client wanted it to be done in that manner, so
>> > that they could put in on the web if required. I advised them about the
>> > design decisions they could consider, but they are clear about what they
>> > want.
>> > The popup was exclusively requested by the client. The app has a module
>>
>> The popup might be blocked by the user.
>> [...]
>>
>> > I'm not religious about any single web technology and if I feel
>> > comfortable
>> Feelings are irrelevant here.
>>
>> > with a certain decision, I go ahead with it. Though I obviously try to
>> > make
>> > use of the newest technologies available,
>> Reminds me of a guy who "upgraded" the doctype to a newer version.
>> Newer doctype. Must be better. Lets do it. I call this fallacy "appeal
>> to new technology". Applies to anyone who served XHTML as text/html.
>>
>> because most of the time, the
>> > technology's there because its better than the ones before it.
>> > I really appreciate your advice, but let's talk more about the proposal
>> > I
>> > made.
>>
>> Your proposal is only justified by the problems that you created using
>> your comfortable methodologies. So "don't do that then".
>> http://www.catb.org/jargon/html/D/Don-t-do-that-then-.html
>> --
>> Garrett
>> Twitter: @xkit
>> personx.tumblr.com
>
>
Received on Sunday, 23 September 2012 16:17:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:00 GMT