- From: Bruno Racineux <bruno@hexanet.net>
- Date: Mon, 04 May 2015 17:26:14 -0700
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: fantasai <fantasai.lists@inkedblade.net>, Simon Pieters <simonp@opera.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Florian Rivoal <florian@rivoal.net>, Chris Lilley <chris@w3.org>, www-style list <www-style@w3.org>
On 5/4/15 8:45 AM, "Brad Kemper" <brad.kemper@gmail.com> wrote: >On May 3, 2015, at 5:45 PM, Bruno Racineux <bruno@hexanet.net> wrote: > >>>> On May 1, 2015, at 3:36 PM, Bruno Racineux <bruno@hexanet.net> wrote: >>>> >>>> If the feature resets to the previous origin. Why not call it like it >>>> is: >>>> 'origin'? Or 'reset-origin'. But 'reset' doesn't have much value >>>>either. >>> >>> IMO, 'origin' adds to the confusion, because it makes me wonder, "what >>> origin"? >> >> That's the intent. Just like you need to know what 'initial' means. > >The intent is to add confusion??? The intent is to be informed. 'Origin' is one of the fundamentals of the CSS cascade. Learning fundamentals of a language before using it is important... /aside One point here is that 'initial' is a state. 'reset, 'clear', 'wipe', 'fallback' or 'rollback' are actions, not states. It doesn't explain the previous point(s) of origin very well. If no love for 'origin' alone, how about: 'ua-origin','default-origin' or 'back-origin'?
Received on Tuesday, 5 May 2015 00:26:44 UTC