On Sun, Apr 11, 2010 at 05:13:44PM -0400, Bob Rosenberg wrote:
Also IMO the feature should be OFF unless the user SPECIFICALLY
activates it (not set to ON requiring the user to turn it off to
cripple it).
IOW: If you want to have the Browser play Net Nanny then require the
user to give
At 09:20 +0900 on 04/10/2010, Philippe Wittenbergh wrote about
[css-d] Changes how (some) browsers handle the a:visited ps:
In short, those browsers will limit the ways the a:visited state can
be styled. Color, background-color, and to some extend, outline,
border are not affected, as long as
At 07:19 +0100 on 04/10/2010, Philip TAYLOR wrote about Re: [css-d]
Changes how (some) browsers handle the a:visite:
A user-controllable feature within the browser, on the other hand,
would provide a convenient way of working around any deficienc{y|ies}
in the specification(s) whilst still
On Apr 12, 2010, at 6:09 AM, Bob Rosenberg wrote:
Am I reading this to say that font-* (such as style and weight, etc.)
will be ignored and set to the :link value even when different in the
:visited version?
That is correct; any change in the font-* properties will be ignored an the
value
Hi Philippe,
(public service announcement)
Both the next release versions of Gecko (tentatively named Firefox
3.7) and WebKit (Safari 5) will implement changes to the handling of
the :visited pseudo-class. Google Chrome will, I suppose, also
implement this.
The underlying thinking is
May I express a personal wish that this behaviour be under
user control ? Whilst I fully understand David Baron's
rationale for the change, I do not believe that it is the
responsibility of browsers to work around security deficiencies
that arise from the correct implementation of W3C standards.
On Apr 10, 2010, at 3:19 PM, Philip TAYLOR wrote:
May I express a personal wish that this behaviour be under
user control ? Whilst I fully understand David Baron's
rationale for the change, I do not believe that it is the
responsibility of browsers to work around security deficiencies
that
Philip TAYLOR wrote:
May I express a personal wish that this behaviour be under
user control ? Whilst I fully understand David Baron's
rationale for the change, I do not believe that it is the
responsibility of browsers to work around security deficiencies
that arise from the correct
On Saturday 2010-04-10 07:19 +0100, Philip TAYLOR wrote:
May I express a personal wish that this behaviour be under
user control ? Whilst I fully understand David Baron's
rationale for the change, I do not believe that it is the
responsibility of browsers to work around security deficiencies
On 2010-04-10 Philippe Wittenbergh wrote:
In short, those browsers will limit the ways the a:visited
state can be styled. Color, background-color, and to some
extend, outline, border are not affected, as long as you don't
use alpha-transparency (rgba()), change the border-style or
On Apr 11, 2010, at 3:34 AM, Benct Philip Jonsson wrote:
It's not clear to me what this means. Which ones of
the following statements will be true?
1) A rule for :visited won't be used at all if
any disallowed property is used in it.
2) Disallowed properties can't at all be applied to
(public service announcement)
Both the next release versions of Gecko (tentatively named Firefox 3.7) and
WebKit (Safari 5) will implement changes to the handling of the :visited
pseudo-class. Google Chrome will, I suppose, also implement this.
In short, those browsers will limit the ways the
12 matches
Mail list logo
