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

Re: [css-regions] Possible change to the Region interface

From: Elliott Sprehn <esprehn@gmail.com>
Date: Mon, 30 Sep 2013 17:08:54 -0700
Message-ID: <CAPJYB1jAPL12mKzMaEDM-pnTo_Lqk0fPKeS-EgpR6xEHH8tATg@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: "www-style@w3.org" <www-style@w3.org>, Alan Stearns <stearns@adobe.com>
On Mon, Sep 30, 2013 at 3:45 PM, Simon Pieters <simonp@opera.com> wrote:

> On Mon, 30 Sep 2013 17:50:26 +0200, Alan Stearns <stearns@adobe.com>
> wrote:
>  It seems odd that I can get from an Element to a PseudoElement, but
>> there's no way to get back from the PseudoElement to the Element (or find
>> out which PseudoElement it is). Am I missing something?
> It hasn't beed added yet because none of these points from the end of the
> email below have been met yet, AFAIK:
> http://lists.w3.org/Archives/**Public/www-style/2013Aug/0453.**html<http://lists.w3.org/Archives/Public/www-style/2013Aug/0453.html>
>  In any case, it's easy enough to say in a spec:
>> Element implements Region
>> PseudoElement implements Region
>> But the question then is what happens with the NamedFlow.getRegions()
>> call, which is intended to return a sequence of Regions. If those Regions
>> can be either an Element or a PseudoElement, what then?
> You can make the return value sequence<(Region or Element or
> PseudoElement)>
That still requires multiple inheritance, what type do you represent that
as in the C++?

I'd rather we didn't have to implement some kind of abstract common base
class to PseudoElement and Element just for Regions.

- E
Received on Tuesday, 1 October 2013 00:10:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:35 UTC