W3C home > Mailing lists > Public > www-style@w3.org > December 2013

Re: [css-color][filter-effects] (was: Re: [filter-effects] Tainted filter primitives)

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 14 Dec 2013 10:48:11 +1300
Message-ID: <CAOp6jLY_+E_WAoEArKs8XuYEG4kKRfoJabp=exu9U0FpT7S7Kg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Dirk Schulze <dschulze@adobe.com>, public-fx <public-fx@w3.org>, www-style <www-style@w3.org>
On Sat, Dec 14, 2013 at 8:11 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> That's silly.  There's no reason to break currentcolor just because
> :visited is being used.  Plus, depending on implementation strategy,
> actually getting the sanitized color is expensive (as you have to
> rerun style matching, excluding all rules with :visited in their
> selectors).
>

FWIW, it's essential that getting the sanitized value be exactly as
expensive as getting the regular value. Otherwise you open yourself to
timing attacks.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Friday, 13 December 2013 21:48:38 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:17 UTC