W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2012

Re: [whatwg] communicating plugin state (primarily for click-to-play)

From: Josh Aas <joshmoz@gmail.com>
Date: Thu, 14 Jun 2012 01:31:11 -0400
Message-ID: <CALAz3ZCHWZfdSabvDVcgHZLBOfci7d_0jXQnemMegWP1_FrjfA@mail.gmail.com>
To: Peter Kasting <pkasting@google.com>
Cc: whatwg@whatwg.org, ash@ashleysheridan.co.uk, Glenn Maynard <glenn@zewt.org>
Turns out another Mozilla developer did add out-of-content UI for
click-to-play to Firefox, I just didn't notice it because our current
UI is as hard to notice as Chrome's (nearly impossible unless it's
pointed out to you). My experimentation with it didn't turn up
anything new or unexpected.

After thinking about this more I'd like to withdraw my request to add
a property to object/embed elements. It might make things a bit easier
or more clear for web developers, but they can already make sites
behave pretty well if they know what to do. Instead of adding
something to the spec we can probably make do with best-practices
recommendations for site changes.

Thanks for the feedback.

On Tue, Jun 12, 2012 at 4:24 PM, Peter Kasting <pkasting@google.com> wrote:
> On Tue, Jun 12, 2012 at 1:26 PM, Ashley Sheridan <ash@ashleysheridan.co.uk>
> wrote:
>> What about doing what popular plugin blockers do and offer the
>> notification in the area the plugin was intended to be used?
> I was operating under the assumption the UA was already doing that.  Hence
> why we're talking about non-user-visible plugins in the first place.
> PK
Received on Thursday, 14 June 2012 05:35:33 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:43 UTC