oslego
commented
12 years ago One option of doing this is by using the setup() method of the test suite to detect the suitable named flow source container: iframe for IE, div for Webkit. No UA sniffing is required, only feature checking.
The test results page needs to have a clear note that IE 10 supports only iframes at the time of the writing.
mibalan
Internet Explorer 10 partially implements the CSS Regions spec. Apart the smaller than WebKit coverage of the spec, one of the major differences of IE10 is the fact that only -s can be added to a named flow.
Since neither behavior (only accepting non-iframe content or only accepting iframe content for a named flow) is explicitly banned or preferred in the spec, the feature testing should do its best to return meaningful results on both IE10 and WebKit-based browsers.
Most likely fixing this issue will require some refactoring of the test code to detect the supported use case.