| 1 | | Strangely enough, I encountered that the effect depends on the HTML document type header |
| 2 | | |
| 3 | | {{{ |
| 4 | | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
| 5 | | }}} |
| 6 | | |
| 7 | | or |
| 8 | | |
| 9 | | |
| 10 | | {{{ |
| 11 | | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 12 | | }}} |
| 13 | | |
| 14 | | If there's no header at all or if there's header |
| 15 | | |
| 16 | | |
| 17 | | {{{ |
| 18 | | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> |
| 19 | | }}} |
| 20 | | |
| 21 | | this bug disappears. |
| 22 | | Perhaps this is because our HTML is not valid: we are using incorrect |
| 23 | | |
| 24 | | |
| 25 | | {{{ |
| 26 | | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
| 27 | | }}} |
| 28 | | |
| 29 | | header, but plain html, no xhtml. |
| | 1 | I managed to reproduce this behaviour on sample site (archive attached) |