Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Thread beginning with comment 552791
To view parent comment, click here.
To read all comments associated with this story, please click here.
deathshadow
Member since:
2005-07-12

To be brutally frank, if your MLS system doesn't work in Opera over something like CSS, the people coding it probably still have their heads wedged up 1997's arse using presentational markup, no separation of presentation from content, using the STYLE tag and attribute for no good reason, no semantics, tables for layout, endless pointless javascripted asshattery for christmas only knows what or doing CSS' job, or other outdated half-assed methodologies that have zero business on any website written after 1998.

Apart from a 100% min-height bug with a fairly well known workaround, there is no reason for HTML/CSS that works in FF/chrome to be a problem in Opera apart from ineptitude or ignorance on the part of the developer...

Which you could probably find out about really quick by doing a view source and a few cut/paste... if you cut/paste all the text from the page, and compare the size to the markup, if the code is more than 3x larger below 10k or 2x larger over 10k, the developer probably needs to go back and learn how HTML works. Is it a tranny document or filled to the brim with HTML 5's idiocy? (since HTML 5 seems carefully crafted for the folks who until a couple years ago sleazed out HTML 3.2 and slapped a tranny on it -- sure as shine-ola isn't for anyone who practices semantic markup; at best it's a sick buzzword akin to web 2.0... at worst, well...)

There's a lot of really crappy outdated code sleazed out by developers who then have the cojones to complain that their broken outdated idiotic practices and endless garbage javascript, HTML and CSS frameworks not working is the fault of the browsers.

Again, maybe if they pulled their heads out of 1997's arse they wouldn't be having these problems.

... and I'm saying this because I've never seen a multiple listing system that wasn't an absolute train wreck of garbage code built by inept fools who have no business writing HTML in the first place!

Reply Parent Score: 2