W3C home > Mailing lists > Public > www-style@w3.org > April 2014

Re: Styling of search/find-in-page results

From: Elliott Sprehn <esprehn@gmail.com>
Date: Wed, 9 Apr 2014 18:33:32 -0700
Message-ID: <CAPJYB1jeRMYDaAfp9SmjUSA2HQeqjjMKahi_H7+EEvV6c8VMpA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Simon Sapin <simon.sapin@exyr.org>, www-style list <www-style@w3.org>
On Sat, Apr 5, 2014 at 9:29 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Fri, Apr 4, 2014 at 12:11 PM, Simon Sapin <simon.sapin@exyr.org> wrote:
> > On 04/04/2014 19:47, Tab Atkins Jr. wrote:
> >>
> >> On Fri, Apr 4, 2014 at 7:31 AM, Zack Weinberg <zackw@panix.com> wrote:
> >>>
> >>> If the PDF.js team would take the time to write up their use cases in
> >>> detail--both what is needed, and how it would most conveniently
> >>> work--that
> >>> would be very helpful to the cause of getting ::selection and friends
> >>> specified. Right now we don't have a good sense of how it _should_
> work.
> >>
> >>
> >> In particular, the pain points are about what elements ::selection
> >> should show up on when a selection spans across elements.
> >
>


We definitely need to make sense to ::selection. Right now the behavior
makes our implementation complex and is also frustrating as a developer.

<div>foo<span>bar</span></div>

div::selection {
  background: red;
}

The text in the <span> doesn't get the color, worse even input::selection
breaks this and somehow magically the selection also applies down into the
ShadowRoot that contains the text which you can't model yourself if you
made a <rich-editor> web component.

- E
Received on Thursday, 10 April 2014 01:34:39 UTC

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