Excuse me for chiming in here but whoa...what a novel idea; a browser that can shift rendering engines on the fly or at least with a single restart. The closest thing I've ever seen to this concept is the IE Tab extension for Firefox where it basically wraps a Firefox Tab with the Firefox GUI (chrome) around whatever version of IE you have on board. For all intensive purposes, it's just IE (all options, functions and features) with a Firefox UI. However, as a remarkable achievement as this extension is, it doesn't quite qualify as Firefox shifting rendering engines to IE's Trident but rather wrapping Firefox's chrome around an IE process within a tab.
Just brainstorming here...something like the above /might/ be possible; ie: wrapping Chrome's UI around a Firefox (Gecko), Internet Explorer (Trident) or Opera (Presto) process much like the above IE Tab extension does for Firefox but you'd have to have those two non-IE browsers actually installed in order for this to happen. What you would ultimately end up with is a single interface for all 3 browsers (but only within a Windows environment since IE is hardly available in OSX or a Linux distro). Not the same thing as you're saying (I believe or is it?) but it seems to me that the Chrome Developers would literally have to have these different rendering engines installed into Chrome (except IE of course which would eliminate the Trident rendering engine for website developers using Macs and Linux boxes) and then rewrite the entire browser once for each different rendering engine utilized and incorporate some method for the user to invoke each "version" when they wish to shift engines with, at most, a browser restart. Now if you're thinking of just utilizing Chrome as a single interface for IE, Opera and Firefox and hence their respective rendering engines within a Windows environment, you might get the developers to think about it but if you're running along the lines of actually incorporating these different rendering engines as part of Chrome itself, I really don't think you'll have much luck (man, that would make for one huge browser). Besides the obvious problems such as the Presto and Trident engines being "closed source" and not available for public use, it's not the rendering engine that makes or breaks a website...it's how a given rendering engine is utilized within the browser that makes the difference. Still, what a unique idea. On 10/4/2008 2:29 PM, gabydewilde wrote: > On Sep 30, 5:28 pm, Darkflame<[EMAIL PROTECTED]> wrote: > >> Wait...your complaining that chrome's javascript is too fast ?[snip] >> > > On Sep 23, 8:52 pm, eleifsp<[EMAIL PROTECTED]> wrote: > >> First, and I'm not trying to be mean, but why are you using Javascript >> for an animation .[snip] >> > > Do I seriously have to explain what an example is? whaaaaaa?????? > > "A problem or exercise used to __illustrate__ a principle or method." > http://www.answers.com/example > > Some people tend to get the example confused and pretend it to be the > actual subject. My website is not the only website on the internet. > > I have to test my website in other RENDERING ENGINES. And each > RENDERING ENGINE has it's own features. Some websites do not work in > other RENDERING ENGINES. Most RENDERING ENGINES can be embeded into > application. > > This is hard to understand???? Why is that? It seems so simple? > > Here, perhaps I'm doing something wrong and this explanation is better > for you: > > http://groups.google.com/group/google-chrome-help-suggestions/browse_thread/thread/135682fc4d27e3bb/c96d0954d609d4ee?hl=en&lnk=gst&q=rendering+engine > > Good luck, > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
