ECatsBlog
  • Home
  • Web Dev
  • Reviews
  • Thoughts
  • ASP
  • SQL
  • Browser
  • Mobile
  • Cloud
  • CMS
  • ECommerce
  • App Hacks
  • Fixes
  • Mapping
  • 3D Printing
  • XAML
  • SEO

Categories

  • 3D Printing (1)
  • App Hacks (4)
  • ASP (20)
  • Browser (12)
  • Cloud (10)
  • CMS (7)
  • ECommerce (6)
  • Fixes (3)
  • Mapping (1)
  • Mobile (12)
  • Reviews (70)
  • SEO (9)
  • SQL (12)
  • Thoughts (59)
  • Uncategorized (1)
  • Web Dev (92)
  • XAML (9)

Archives

  • February 2022 (1)
  • June 2019 (1)
  • January 2019 (175)
  • December 2018 (47)

Browser Power

When Written: April 2007

When I talk of a future browser for web applications, I would like to make a plea to the various browser developers. How about having a basic browser engine, that is open source and free to use that is fully standards compliant?

Here I am talking just about the rendering engine, the bit between the multitude of tool bars that everyone seems to want you to install until a point arrives that you end up reading web pages through a virtual letterbox, and the status bar at the bottom that few of us look at. This engine could be used inside a browser wrapper user interface, where different companies could add their own enhancements to the user experience. Like tabbed browsing, quick searches, toolbars, popup blockers etc, but nothing that would affect the rendering of web pages would be allowed.

This browser engine could then also be used as the rendering engine in the various development tools out there so developers would at long last have a dev tool that previews a web page exactly as a browser would. Utopia? Perhaps! But not impossible to achieve. We are nearly there with the Mozilla project but it just needs a realisation that consistency in the browser rendering is what is needed, not differing interpretations of the standards. The only browser differences we should have should be in the extra functionality for the user, and not in the rendering of web pages, the running of JavaScript nor in the document object model. In the past certain browsers had extra technology in them to enable support for certain intranet technologies.

Hopefully web technology has matured to such a point that things could be consolidated and all involved can see the benefit of a browser that will work with ALL web sites, as well as having development tools that render designs correctly?

Article by: Mark Newton
Published in: Mark Newton

  • Previous Browser Detection4 years ago
  • Next Greedy software4 years ago

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • SMTP Email Client
  • IIS8 SMTP setup
  • 3D printing the Ness of Brodgar
  • Which phone is best?
  • Mobile Apps

Recent Comments

  • Quality assurance services on Windows 10 phone and HERE Maps – Fixed!
  • HP Deskjet 3755 Wireless Printer Setup on Windows 10 phone and HERE Maps – Fixed!
2022 ECatsBlog. Donna Theme powered by WordPress