Talk:Web browser engine
|This article is of interest to the following WikiProjects:|
- 1 SecurityFocus cite
- 2 Layout managers
- 3 Terminology
- 4 Article name should be "Layout engine" not "Web browser engine"
- 5 Move discussion in progress
- 6 If Layout Engine redirects here, where do I add information about thick client (non-web) layout engines?
- 7 Time to update statistics - a "little wrong"
- 8 Statistics (combine Mozilla with Firefox?)
- 9 Layout engine stub
I think there is no article on layout managers in Wikipedia. What I intend by layout managers is what is done in Java Swing in LayoutManagers, or the Box model in XUL, etc... Almost evenry layout engine use a sort of automatic layout at the base. It can be difficult to understand for people that are not familiar with UI development. I would like to create a new article on this subject, and linking this article to this one, and maybe swing, C#, XUL, etc... What do you think ? Hervegirod 09:57, 14 May 2006 (UTC)
It may be useful to render the reader aware of the fact that the terms "layout" and "rendering" are used in an overly broad meaning in this context.
A so called "layout engine" does in fact a lot more than layout. The basic tasks performed are: 1. document retrieval from the network 2. parsing 3. creation of the document tree 4. layout 5. rendering 6. event handling / scripting.
The layout proper is only the computation of the position of every graphical elements on the page. You find layout modules in a lot of programs, like EDA tools, TeX, graphviz, ...
The rendering proper is only the transformation of graphical objects (bitmap images, vector graphics, text) to a raster. Likewise, you'll find a renderer in a lot of programs, like ghostscript, flash, ...
What do you think ? Tonigonenstein 02:31, 15 September 2006 (UTC)
- I completely agree, and had gone to the talk page to make the same point made in your paragraph 3. Formerly the IP-Address 184.108.40.206 21:56, 5 May 2007 (UTC)
- That might address a remark I was about to make. If this is about rendering marked up content, why is Ghostview not in the list? Or any dvi viewer? or a postscript or pdf viewer? Those all take a structured language as input, and render the result... I think that is clearly not what was intended, so can this please be clarified? Hugo, 220.127.116.11 (talk) 19:24, 16 March 2010 (UTC)
- I have taken the bold step of renaming this article to web browser engine, which is what it is really about. The term is how Webkit describes itself. I also explain in the article the difference between layout, rendering and web browser engines so that should solve the issue. Then articles for layout engines and rendering engines in general can be created and reference this one. Barsamin (talk) 01:51, 25 May 2010 (UTC)
I came to this page to find out which standards organization defines the web browser engine. I think it is WWWC, but am not 100% sure. I was surprised that it is such a small page and that it didn't identify the standards organization. — Preceding unsigned comment added by 18.104.22.168 (talk) 17:04, 7 July 2012 (UTC)
- The standards organization, the WWWC, defines HTML5, CSS3 and other standards. The browser layout engines attempt to implement the standards. LittleBen (talk) 05:18, 19 July 2012 (UTC)
Article name should be "Layout engine" not "Web browser engine"
Move discussion in progress
There is a move discussion in progress on Talk:Comparison of web browser engines which affects this page. Please participate on that page and not in this talk page section. Thank you. —RMCD bot 18:13, 3 November 2012 (UTC)
If Layout Engine redirects here, where do I add information about thick client (non-web) layout engines?
I want to add content to Wikipedia about the differences between the thick client layout engines found in WinForms, WCF, Linux, Java, and other OS's. If we insist on redirecting "layout engine" to here, then where do I put it? It looks like there was already a discussion (link above) - did we decide to intentionally exclude the subject? Contrary to popular opinion, not all user interfaces are web-based. — Preceding unsigned comment added by 22.214.171.124 (talk) 19:35, 12 November 2013 (UTC)
Time to update statistics - a "little wrong"
Statistics are probably right but old, however at the time Chrome probably used WebKit, not Blink. Blink was released in Chrome 2013-06-17 in Linux and next month on other platforms. As it is a fork of WebKit then not a huge deal. comp.arch (talk) 13:46, 3 March 2014 (UTC)
Statistics (combine Mozilla with Firefox?)
Is Wikimedia (name it Wikipedia per WP:COMMONNAME) data the best and representative?
See my latest edit to this page. See my section: Talk:Usage_share_of_web_browsers#Wikimedia_number_do_not_add_up_.28to_100.25.29. Please discuss there. Note that my latest edit here contradicts that page. comp.arch (talk) 22:20, 5 March 2014 (UTC)
Layout engine stub
There appears to be a vary small stub article under the title Layout engine. This article (Web browser engine) asserts a "web browser engine" is sometimes called "layout engine". And if this is the only usage of the term layout engine then I suggest a deletion of the stub article. --Devin Murphy (talk) 19:02, 28 January 2016 (UTC)