“accept” attributes are definitely not supported in Microsoft Edge at this point. I confirmed your behavior as “no go” in edge, but showing up in IE via the […] thing in the upper right of Edge. The Edge status shows it as “Under Consideration” with just 198 votes at https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/13661175-full-spec-support-for-accept-in-input-type-file . If you’re interested in … Read more
This will solve the issue. // Fix: Expected server HTML to contain a matching <a> in const renderMethod = module.hot ? ReactDOM.render : ReactDOM.hydrate; renderMethod( <BrowserRouter> <RoutersController data={data} routes={routes} /> </BrowserRouter>, document.getElementById(‘root’) );
It seems that it’s part of Chromium’s GREASEing strategy: User agents’ brands containing more than a single entry could encourage standardized processing of the UA string. By randomly including additional, intentionally incorrect, comma-separated entries with arbitrary ordering, they would reduce the chance that we ossify on a few required strings. Looking at the Chromium repository, … Read more