None of my issues with Edge have anything to do with the browser engine.
All of them have to do with stupid Microsoft like decisions, like ‘you can’t avoid the internal pdf reader’.
Microsoft is building a Chromium browser to replace Edge on Windows 10
471–480 of 774 posts
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#472Earlier quoted context omitted.
> I'm not sure what more they could do. Don't release a browser which cannot be made to adblock. I suspect that 90% of the vaguely techy world laughed at Edge the moment it's clear they'd have to accept autoplaying videos on webpages again. And like it or not those reactions filter through family and friends pretty effectively.
Doesn't Edge have AdBlock and uBlock extensions?
It didn't for a long time.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#473Earlier quoted context omitted.
http://modern.ie Free Windows VirtualBox images you can use for testing!
You've used these, right? It's an enormous pain to have to spin up a separate VM per version of Edge/IE to get a "Your copy of Windows might be stolen" message and have some finite period of time to test. I appreciate that they have these, but it's a real annoying hoop to jump through, and I've long suspected the hope is you'll just have your company buy a cheap windows box for testing. I can test the other browsers…
How do you test Safari without an Apple device?
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#474Earlier quoted context omitted.
Maybe OP is mainly referring to the recent update issues where entire folders have been delated as part of the "forced" updates.
I've had to fix friends' computers who had their user profiles corrupted by an update so they can't log in.
> I've had to fix friends' computers who had their user profiles corrupted by an update so they can't log in.
An extremely recurrent issue with windows 10 updates (in particular, the big ones that happen every six months and behave like a complete OS reinstall) that manifests in so many different forms.
I've seen it do stuff like only breaking UWP apps while leaving everything else intact. I've seen it break UWP apps + the start menu. And then I've seen it do the login breaking thing. The thing those symptoms have in common is that they were always solved by simply making a new user profile and logging into it then transferring the user data into the new profile, proving that the root of all horrors comes from bugs in the user profile migration that windows does during updates.
I'm always horrified by the process not just because of the bugs but also because of how inane UWP is. Every new profile created will also get its amazing share of UWP crapware downloads, because of course it wouldn't make sense for software to be installed system wide, nah let's do that every time a profile is created and let's pull the microtransaction ladden mobile games while we're at it. Creating user profiles takes so much time on older acquaintance computers with spinning rust too.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#475(Disclaimer: I work at Microsoft.)
This is a good move. Microsoft is further embracing open source technology. I really want to use Edge, I gave it so many tries, but every time I keep coming back to Chrome because Edge is just so damn unreliable. And Chrome is creepy as hell. And Firefox just... is slow and not smooth. A not-creepy web browser from Microsoft, with the same reliability and speed of Chrome? Sign me up.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#476Anyone here use edge for epub reader?
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#477As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.
Headed? We've been there for quite some time and this was piloted by Google itself. It's been years since they started to do the "works better in Chrome" and blocking features if you are not in Chrome (or, to be more specific, if you are not using chrome UA).
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#478Earlier quoted context omitted.
It's not really better though - having only two real browsers is not good for open standards or the open web. This will be especially true when Firefox inevitably shutters it's in-house efforts in a couple of years due to the amount of sites that won't work with it , and starts using Chromium too. Staring into my crystal ball tells me Firefox will become "janky" in the eyes of users on account of how many sites don't…
> This will be especially true when Firefox inevitably shutters it's in-house efforts in a couple of years due to the amount of sites that won't work with it, and starts using Chromium too. Watching Mozilla align Firefox's extension API with Chromium's, I'm a little surprised that they haven't already made the move. If browser evolution continues along the current path, I predict Firefox will switch to Chromium withi…
I use Firefox as my primary browser and I don't find mainstream websites glitchy at all.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#479That's quite unfortunate. I like Edge - the rendering engine, not so much the browser. If Edge would let me sync my bookmarks with Firefox, I would switch immediately. I found it quite fast, and no other engine works so well with touch. I also don't recall rendering problems.
What MS should do IMHO is to package Edge as a component (like IE was in the old days), and let people build shells around it (like the Maxthon browser was).
I don't think I would use an Edge based on Chromium much, as I liked the UI itself not so much.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#480Earlier quoted context omitted.
There was nothing "broken" about it. It was just non-standard at the time, but the old standards were wrong, like they were on many matters (floats for layout, for example, was a load of shit).
Floats were just supposed to be used to control text floating around images and other inserts. It was never designed as a general-purpose layout mechanism.
Sure, but that's largely because standards bodies chose not to introduce a general purpose layout mechanism despite it being very clear from 1990s websites that the need existed, and instead focused on deprecating layout elements from HTML and persuading developers CSS was the only valid way to do layout.