If the Gecko engine is the same as that used in Firefox, why are some CSS not rendered correctly (as per Firefox)? Examples: inline-block treated as block, same for inline-table and a mysterious problem with disappearing floats.
Maybe some different settings in the prefs? But perhaps rather the newer Gecko engine in current firefox. KM has yet a bit catching up to do there, but from what I read there were too drastic changes between gecko 1.8 and 1.9, that makes things rather complicated, for the only 1-2 current KM developers who do this in their spare time. Oops, rethinking again, I learned just recently that KM does NOT use the firefox gecko, but the seamonkey gecko! But still the same problem with that major gecko change.
There are a couple of things that might come into play here. One is that KM and FF no longer use the same engine. KM uses the engine from the SeaMonkey line. Two is how you noticed the difference. If you use FF the web site might send a different version of the file than if you use KM. They should not send different code but I don't know accuracy of their sniffer code.
Try to see the site with a SeaMonkey user agent and compare.
there are a lot of advances in css rendering in gecko 1.9 but nothing really that will make a site unreadable or effectively change the layout with a 1.8 engine.. it's mostly things like text manipulation and special effects.. the main difference that can actually mess up rendering is css transforms which isn't supported at all by 1.8 .. very few sites have impemented css transforms and just for testing/developing etc.. it's not a widespread thing yet.
the most likely reason is that a website not identifying kmeleon as a gecko browser and sending it to a wrong(ie) or older css file.. try changing the useragent (tools>useragent) to firefox and see if there are still differences.
The inline-block elements displaying as block are definitely not browser sniffing problems because I created a couple of simple webpages on my local server to verify before posting.
In 2009 (December 01, 2009 06:14PM) the initial assumption was that Firefox and K-Meleon had the same Gecko engine and thus the same CSS layout. At that time most Firefox browsers did AFAIK not have the same Gecko engine anymore.
We were fully aware that some pages did not support Gecko 1.8 then and some pages had faulty browser switches and send users a page coded for another browser.
So the question: "Hi, was this problem ever fixed ? I am seeing it with the latest version of k-melon." is IMHO a bit off mark.
So this was never a K-Meleon bug to be fixed. & I wonder whether these page owner fix their pages and their browser switches & whether anyone went there to remind them.
It definitely lets me switch menu items (starting left to right or out of order) with 1.5.4 and 1.6beta2. No idea why You do not have the same results with 1.5.4. My guess customizations in my version.
With K-Meleon 1.5.4 it also has some CSS glitches/errors due to the older CSS implementation.
Example: 1.5.4 cannot go to Customize, Submenu: Themes and Upgrades.
They vanish before they can be chosen.
With K-Meleon 1.6beta2 this problem is not encountered.
The menu item Online Maual shows errors in both K-Meleon versions.
1.6.b2 shows the same errors as FF with 1.9.x and 2.0 engine.
1.5.4 shows the errors differently.
Since they appear in all Gecko based browsers they are IMHO site specific errors.
Edited 1 time(s). Last edit at 04/05/2011 03:38AM by guenter.
Please try with a new profile in K-Melon 1.6beta2.
Check that you have JavaScript enabled, Tools -> Privacy -> Block JavaScript (unchecked)
Are you using some extension, as adblock plus or noscript?
Are you using some Adblock CSS filter or User-Defined StyleSheet?
What Windows version are you using?