There are rendering differences in the mainline that have yet to make it in to the version Chrome is using. They're both forks from the main version and they're both heavily customized to improve the performance in ways that each browser development team thinks is meaningful for their end found a great bug in the Chrome bug database that gives us the final clue that it's down to WebKit forks: - that bug is talking about the differences between the fork in Chrome and the mainline of WebKit from the open source project. The rendering engines are a big part of each browser's secret sauce.īoth Safari and Chrome use WebKit, but the similarities between the WebKit instances they use stop somewhere around the name of the engine. So they get the full OS-level emoji-expansion treatment.īut what happens inside a web browser window is all very browser dependent. The window UI elements are likely (emphasis on likely, I may not be correct here) all being rendered by the OS. But the Window UI elements (the tabs in Chrome) are okay. We know Safari renders the character set differently than Chrome. The difference is the rendering engines for the browser windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |