Bugs :
K-Meleon Web Browser Forum
If I specify a background image with css in this manner
body {
background: #fff url(/images/LeftBorder2.png) no-repeat fixed 10px 0px;
}
the image will be fixed, if the content-type of the page (XHTML 1.0 strict) is text/html. On the same page with content-type application/xhtml+xml, the image scroll down and a subsequent scroll up cause a fragmented background image.
A test case can be found here:
Content-type: text/html
www.cetaceen.de/test/bgimg.html
Content-type: application/xhtml+xml
www.cetaceen.de/test/bgimg.xhtml
Mozilla 1.2a shows the background image in both cases correct.
m.m
It does the same thing in Mozilla 1.1, which the new beta is based on.
If it works in Mozilla 1.2a, then maybe mozilla has fixed the problem.
This seems to be fixed in Mozilla nightlies so I hopefully we can expect it to be fixed in next KM build, if it will incorporate relatively latest Mozilla engine.
You can talk about issues with k-meleon here.
css: background no-repeat fixed and application/xhtml+xml
Posted by:
Mario Mueller
Date: September 29, 2002 09:55AM
If I specify a background image with css in this manner
body {
background: #fff url(/images/LeftBorder2.png) no-repeat fixed 10px 0px;
}
the image will be fixed, if the content-type of the page (XHTML 1.0 strict) is text/html. On the same page with content-type application/xhtml+xml, the image scroll down and a subsequent scroll up cause a fragmented background image.
A test case can be found here:
Content-type: text/html
www.cetaceen.de/test/bgimg.html
Content-type: application/xhtml+xml
www.cetaceen.de/test/bgimg.xhtml
Mozilla 1.2a shows the background image in both cases correct.
m.m
Re: css: background no-repeat fixed and application/xhtml+xml
Posted by:
Jason Foss
Date: September 29, 2002 11:51AM
It does the same thing in Mozilla 1.1, which the new beta is based on.
If it works in Mozilla 1.2a, then maybe mozilla has fixed the problem.
Re: css: background no-repeat fixed and application/xhtml+xml
Posted by:
sven
Date: September 30, 2002 07:28PM
This seems to be fixed in Mozilla nightlies so I hopefully we can expect it to be fixed in next KM build, if it will incorporate relatively latest Mozilla engine.
English