- From: Karl Dubost <karl@la-grange.net>
- Date: Thu, 2 Apr 2015 17:50:21 +0900
- To: Simon Pieters <simonp@opera.com>
- Cc: "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Kyle Simpson <getify@gmail.com>
Le 2 avr. 2015 à 17:36, Simon Pieters <simonp@opera.com> a écrit :
> On Wed, 01 Apr 2015 06:57:43 +0200, Kyle Simpson <getify@gmail.com> wrote:
>> There are features being added to the DOM/web platform, or at least under consideration, that do not have reasonable feature tests obvious/practical in their design.
>
> I think we should not design a new API to test for features that should already be testable but aren't because of browser bugs.
Agreed with what Simon is saying.
All these are really bugs in detectability and implementations of the features.
https://github.com/Modernizr/Modernizr/wiki/Undetectables
What we could do is try to increase the granularity of the API/tests if the API is too shallow for detecting what is useful.
Adding another meta layer of testing makes the Web Compatibility story even harder. As usual, we look at the good side of the story as in it will help us make better site, but what I'm seeing often is more on the side of
What is the hook that will help us to say 'Not Supported'
because our project manager told us browser not below
version blah.
(Based on sad true story. Your perpetual blockbuster)
--
Karl Dubost 🐄
http://www.la-grange.net/karl/
Received on Thursday, 2 April 2015 08:50:55 UTC