ID:1319803
![]() Jul 10 2013, 4:00 am
|
|||||||
| |||||||
This would be an excellent replacement for the current shitty IE controls. It packs 24mb but that shouldent be a problem in this day and age. Its really easy to intergrate too.
|
As ATHK said, between our range of users and the actual benefit of such a feature, it just isn't realistically worth the dev time (However short it may be).
|
The implementation in my engine is only 100 lines of glue code, it shouldent take too much time to add assuming it compiles and the way controls work is sane
|
I'd only like to see this feature as an optional thing, I personally can't download 24MB of extra crap every time BYOND has an update. Not everyone has access to full-on broadband, even in "this day and age".
|
BYOND is 3.5MB or so right now. 14MB isn't too terrible, but still a bit much for my poor ol' connection. Having a real browser would be nice -- except it would break older games who designed their browser interfaces around IE's limitations. I'd imagine there would have to be some kind of backwards compatibility for things like that, but since embedded IE doesn't cost any extra size on the package I don't see why it couldn't fall back on IE in older compiled games.
|
Considering that right now it may use 4 different IE versions, each with different problems, I dont think it'd break anything that isnt broken
|
It actually uses IE7 at the most, it's forced into compatibility mode on embedded applications if the client has a higher version. At least it did last time I asked, and there wasn't an easy way around that.
It's not a bad thing though, it lets developers focus on a specific IE version and play from there, people with IE6 still installed can be notified to upgrade or live with things not quite working as expected. Generally though, on BYOND you design your browser stuff with IE6 in mind solely because it's still the most common version of IE being used by the common user, but it's waning out to IE7 -- finally. |
The new pager doesnt even work on IE6 anymore (apparently), so theres no reason to support it anymore
|
Bumping this as people are having OS-specific issues with Javascript in IE (breaks on Win8)
|
Honestly, I'm not a fan of the idea of supporting multiple browsers at all.
Developing CSS and javascript applications for use in BYOND is rough enough without having to constantly second-guess what the client is going to be seeing. IE might be wrong on how it interprets and displays just about everything, but the behavior can be accounted for. Unfortunately, microsoft really screwed the pooch, as it were, when it comes to CSS by making sure that IE10 doesn't recognize browser-specific CSS hacks, which breaks about 90% of the websites built after 1993. I'm quite content with deploying for IE7, because I know that anything I make will display exactly the same for all clients. |
Thats the whole point of this, switching the browser panels to a sane browser system
Right now IE DOESNT actually display the same for all clients, it breaks things on Windows 8 |
Why are we using Chrome?
Shouldn't instead we be looking to use Geko's rendering engine? The same engine Firefox uses? https://developer.mozilla.org/en-US/docs/Gecko/ Embedding_Mozilla |
This will end up with an argument that goes around and around..
Anything that isn't IE would be great.. |
Honestly, anything that isn't IE is going to be better. Chrome (and by extension, Opera), and Firefox are pretty neck and neck with their support of the HTML5 and ECMAScript 5 specifications, with a few minor differences. Compared to Internet Explorer who is always ten steps behind when it comes to adhering to any sort of standard.
|
CEF is used by quite a lot of things, is really easy to use and generally seems to be more grown up, personally I havent tried embedding firefox but by a quick look it looks extremely messy and complex
|
That being said I don't even know if they could include it in BYOND since they are using a really old legacy compiler? Correct me if I am wrong here..
You have my support, though I don't see it actually being taken into consideration.