Forum Discussion
Windows 10 1903 'Welcome to Windows'
It might be something that goes all the way back to the original Chromium Prime. This is how it looks on Google Canary Chrome (77.0.3852.0) which like Microsoft is the one step up from the original Chromium Prime version that they're open sourcing from.
Yeah, this is how it looks on Chromium (77.0.3853.0) which is the prime "right off the truck" version that comes before the Canary builds. It looks the same. Although interesting that that Original Edge doesn't have that issue...what about Internet Explorer? Lets find out!
But how can you get back to the "Welcome to Windows" page? https://www.msn.com/spartan/dhpwinfre?country=gb&locale=en-gb&imgh=170&imgw=300&bcnt=3&templatetype=1.1&placement=353689&useIris=1&tcContentId=a51e1cc323404b0782ddbdcdbf573894&tcContentPath=//item[0]&asid=a51e1cc323404b0782ddbdcdbf573894&poptin=&oemname=TOSHIBA&oemid=TOSHIBA&devfam=WINDOWS.DESKTOP&devosver=10.0.18362.239&ossku=PROFESSIONAL&arch=X64&cdmver=10.0.18362.1&fosver=14393&prevosver=16299&isu=0&tl=4&msa=&disphorzres=1600&dispvertres=900&nettype=WIFI&metered=FALSE&moid=&topt=&localid=w:F22B750D-657A-A8FA-2C4B-1D2C1E83FF40&auid=&lo=2080514&tsu=6&flsid=&osbuild=&waasring=&sc-sigimg=&OCID=ems.display.welcomeexperience&CCID=5B1EED13E2E645289FFD9242F65B9CDA&market=GB&enableregulatorypsm=0&enablecpsm=0&ishostisolationenforced=0&targetexperience=default&tabbedshell=0
only opens an msn.com page(albeit titled "Welcome to Windows")
Anthony Noel Burgess Having looked at the different results (renders properly on EdgeHTML, but renders improperly on all Chromium-based browsers (Edge Chromium, Google Chrome and Edge Chromium, renders improperly on Firefox, and renders not at all on IE 11) it looks to me like the page was designed using EdgeHTML-specific elements of some sort.
It probably isn't worth worrying about -- it isn't an Edge Chromium problem -- but Microsoft should take the time to rework the code so that the page renders properly on Blink, EdgeHTML and WebRender engines. Website design 101.
tomscharbach - Yeah I see what you're saying now. Thus probably why it looks fine on Edge but the other browsers it looks the way it looks. I'm guessing they will at some point have to adjust that so the web page appears properly on the new edge browser. I don't use IE 11 anymore at all since 2016 (and I was one of those using IE since IE 1.0 came out). But seeing it didn't appear at all in IE indicates what you were saying. I guess like anything else it's all a work in process since Microsoft is starting over from scratch with Edge.
"I'm guessing they will at some point have to adjust that so the web page appears properly on the new edge browser."
Yes, it will. It looks like Edge Chromium is going to be in-built into Windows 10 (replacing EdgeHTML) starting with the Spring 2020 (20H1) feature update, so everything Microsoft (including WebView, which powers web integration in Windows 10 apps) is going to have to be ported over to work with Edge Chromium by then.
"I guess like anything else it's all a work in process since Microsoft is starting over from scratch with Edge."
I hope that Microsoft, this time around, will follow Web Design 101 principles and rework its websites/pages so that the websites/pages work with all the standard rendering engines (Blink, WebRender, Webkit and so on).
If nothing else, the "Welcome" web page issue demonstrates the folly of writing code that is browser-specific.
Microsoft has a habit of doing that -- the myriad of issues created by IE-specific coding come to mind, keeping Microsoft stuck with supporting the legacy (and risky) browser-specific elements of IE come to mind -- and Microsoft should just stop doing it. The days of proprietary browsers is over.
While web technology moves on and requires web developers to constantly update -- think about the issues created by Google Earth's ties to depreciated PNaCl -- developing around browser-specific elements invites unnecessary problems.
With Internet Explorer 11 that first part of the page doesn't load on it:
