Re: The infamous Mozilla core editor

Aceman acelists at atlas.sk
Mon Mar 9 12:47:57 UTC 2015


______________________________________________________________
> Od: Axel Grude <axel.grude at gmail.com>
> Komu: Bron Gondwana <brong at fastmail.fm>, <tb-planning at mozilla.org>
> Dátum: 09.03.2015 13:33
> Predmet: Re: The infamous Mozilla core editor
>
>> *Subject:* Re: The infamous Mozilla core editor
>> *To:* axel.grude at gmail.com, tb-planning at mozilla.org
>> *From: *Bron Gondwana
>> *Sent: *Monday, 09/03/2015 12:00:19 12:00 GMT ST +0000 [Week 10]
>> On Mon, Mar 9, 2015, at 09:04 PM, Axel Grude wrote:

>> I think that CSS is generally a bad idea where your content is likely to be embedded 
>> somewhere else (webmail or even just a UI which uses HTML itself on a desktop).
>> The problem with CSS can be spelled out in two words: global variables.  Styles are 
>> global variables, and even if you prefix them with something unique, anybody 
>> consuming your content is required to validate all your names to make sure they 
>> don't tread on not only anything in the surrounding code, but also any other 
>> messages which are being rendered in the same context. It's a horror.
>well there is the child selector (>) so maybe this could be used to somewhat alleviate 
>this. But another problem is that if you quote and your style definitions happen to be 
>in an area you "snip out" you have the added problem of potentially losing your 
>styles. So Composer needs to keep track of these and move them around.
>
>> If only there was a way to specify styles as being lexically namespaced to a DIV - 
>> you could just wrap your email in a DIV, set styles on it, and use them inside to 
>> your heart's content, with simple short names or just style the existing semantic tags.

Isn't this what "scoped" <style> is for? http://www.w3schools.com/tags/att_style_scoped.asp
Despite of what the page indicates, I have also seen IE support <style> placed inside <body>, even without the "scoped" attribute.



More information about the tb-planning mailing list