Re: features at risk spreadsheet

Hi Thomas,

That's a short URL that redirects to OneDrive:
https://onedrive.live.com/view.aspx?resid=FD9E7123283F274C!594647&ithint=file%2cxlsx&app=Excel&authkey=!AIguPi1fOc66FII

(possibly OneDrive is blocked on your firewall because it's a generic file
sharing service, who knows what naughty files might be there?)

I've attached the current values of the spreadsheet as an Excel file.

~ABR

On 17 May 2018 at 16:24, Smailus (US), Thomas O <Thomas.O.Smailus@boeing.com
> wrote:

> I cannot get at https://1drv.ms/x/s!AkwnPygjcZ79pKVXiC4-LV85zroUgg
>
> My IE browser says “This page can’t be displayed
>
>
>
> •Make sure the web address https://1drv.ms is correct.
>
> •Look for the page with your search engine.
>
> •Refresh the page in a few minutes.”
>
>
>
> If it’s on a file sharing platform, it is highly likely Boeing has blocked
> access to the domain at the firewall.
>
> Is there some way to get read access to this data via the W3C sites?
>
>
>
> Thomas
>
> --
>
> Thomas Smailus, Ph.D.  P.E.
>
> Boeing Information Technology
>
> thomas.o.smailus@boeing.com
>
>
>
> *From:* David Storey [mailto:david@openweb.io]
> *Sent:* Sunday, May 06, 2018 19:40
> *To:* Liam R. E. Quin <liam@w3.org>
> *Cc:* public-svg-wg@w3.org
> *Subject:* Re: features at risk spreadsheet
>
>
>
> As the whole changes section is big, and you can get bogged down with all
> the various editorial changes and things that are already supported, I’ve
> created a reduced spreadsheet with just the DOM interfaces that I know are
> not well supported (checked tests where available, WebIDL files and type
> mirror). It lacks things like CSS features and presentational attributes.
> The smaller changes like changed behaviour we can probably look at once
> we’ve made the first cut of removing things in this spreadsheet. They’ll be
> easier to test than things like hashes and meshes.
>
>
>
> https://1drv.ms/x/s!AkwnPygjcZ79pKVXiC4-LV85zroUgg
>
> I’ve made it editable in case any one wants to add something or change
> browser support
>
>
>
> I’ve marked the features I’m planning to look into implementing in Edge as
> “Intent”. The FALSEs just means a browser doesn’t support a feature and not
> a statement of no intent. crossOrigin for example is probably something
> we’d want to do at some point to be consistent with HTML.
>
>
>
> David
>
>
>
> On 5 May 2018, at 11:16 am, Liam R. E. Quin <liam@w3.org> wrote:
>
>
>
> i made a spreadsheet [1] listing all the changes from L (changes), with
> whether we have tests, whether it's testable (i think) and somenotes in
> some cases on why i think it isn't :), and whether it's at risk.
>
> For sure it could be improved, but the big problem is i've so far only
> been through the first two sections in detail.
>
> If you (anyone) have a few moments to update it by adding whether there
> are tests, or whether specific features should be marked at risk, that
> would be great; it'll give us more concrete data for our conference
> call.
>
> Or if i'm out to lunch tell me that too and i'll share my sandwi...
> er.... or whatever :)
>
> Liam
>
> [1] https://ethercalc.org/721eaqkprvhx
>
> --
> Liam Quin, W3C, http://www.w3.org/People/Quin/
> Staff contact for Verifiable Claims WG, SVG WG, XQuery WG
> Improving Web Advertising: https://www.w3.org/community/web-adv/
> Personal: awesome vintage art: http://www.fromoldbooks.org/
>
>
>