GithubHelp home page GithubHelp logo

Status of incubation about inert HOT 4 OPEN

marcoscaceres avatar marcoscaceres commented on July 20, 2024
Status of incubation

from inert.

Comments (4)

robdodson avatar robdodson commented on July 20, 2024

Tagging in @alice and @bkardell for their thoughts

I don't know of any plans to do additional work with the wicg/inert repo. It's mostly become a place to hold the code for the polyfill. Once inert lands in Firefox I was going to add a note to the readme to recommend that people stop using the polyfill, similar to what we did for focus-visible

from inert.

bkardell avatar bkardell commented on July 20, 2024

I had no plans to incubate something new with regard to inert here. I would like to know what happens/happened with other things like this that have been successful. I mean, I agree with @robdodson below at least

Once inert lands in Firefox I was going to add a note to the readme to recommend that people stop using the polyfill, similar to what we did for focus-visible

but maybe there's a better thing we could/should do -- what do the chairs suggest @marcoscaceres ?

from inert.

marcoscaceres avatar marcoscaceres commented on July 20, 2024

@robdodson suggestion seems great. What we should think about is if we plan to maintain the polyfills and maybe we could sunset those after, say, another a year or two after all browsers have support? That should hopefully give everyone enough time to move away from the pollyfill, plus also an opportunity to fix any last minute incoming/maintenance bugs.

Then we should archive the repos and direct folks to the appropriate W3C/WHATWG place.

from inert.

robdodson avatar robdodson commented on July 20, 2024

What we should think about is if we plan to maintain the polyfills

Since I've left Google I haven't really had time to work on these so, barring any major issues, I wasn't planning to do any further updates. But if other folks have bandwidth to address any maintenance issues that come up, that would be great.

Maybe we could sunset those after, say, another a year or two after all browsers have support?

Sounds good to me. Aside from updating the README once Firefox ships to encourage people to switch to using the built-in version, are there any other things we should do right now to help with the sunsetting?

Then we should archive the repos and direct folks to the appropriate W3C/WHATWG place.

👍

from inert.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.