ricardos4n / base2

Automatically exported from code.google.com/p/base2
0 stars 0 forks source link

Another IE6 weirdness: getComputedStyle and tables #74

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

A getComputedStyle call on the BODY element breaks subsequent calls to
getComputedStyle for elements in a table cell.

Here's the test case:
http://wforms.googlecode.com/svn/trunk/sandbox/base2-IE6-getComputedStyle.html

Code:
    var elem = document.getElementById('bodyElement');
    var p = document.defaultView.getComputedStyle(elem,
"").getPropertyValue('padding');

    var elem = document.getElementById('testField2');
    try {
        var p = document.defaultView.getComputedStyle(elem,
"").getPropertyValue('position');
    } catch(x) {
        alert("ERROR: "+x.message); 
    }
    if(p=='static') alert("OK");

  * It works fine if you remove the getComputedStyle on the body element. 
  * It works fine if the second element is not in a table.
  * It breaks on line 654 in base2-dom.js. A try/catch indicates a problem
accessing the 'rubyOverhang' property. 

Original issue reported on code.google.com by cedric.s...@gmail.com on 7 Jan 2008 at 3:51

GoogleCodeExporter commented 8 years ago
I can't recreate this bug. What version of MSIE are you using? Are you using 
sp1 or sp2?

Original comment by dean.edw...@gmail.com on 7 Jan 2008 at 12:04

GoogleCodeExporter commented 8 years ago
OK. I can create the bug now. It seems that accessing ruby properties causes a 
crash.
Good old explorer! I'm ignoring these properties in future.

Fixed on my machine. Will check in later.

Original comment by dean.edw...@gmail.com on 7 Jan 2008 at 12:16

GoogleCodeExporter commented 8 years ago
For the record it was on IE6 SP2 WinXP.
Ignoring the properties is fine, I'd never heard of the ruby element before.. 

Original comment by cedric.s...@gmail.com on 7 Jan 2008 at 2:50

GoogleCodeExporter commented 8 years ago
IE supports simple ruby only.
http://www.w3.org/TR/ruby/

Original comment by joao.ei...@gmail.com on 10 Feb 2008 at 11:03

GoogleCodeExporter commented 8 years ago
This is now fixed in trunk/lib.

Original comment by dean.edw...@gmail.com on 31 Mar 2008 at 4:53