Re: Seeing the open issues

Taking this back off the HTML list because it really doesn't seem useful 
for the entire 400+ person working group to read my defending myself... :-)

On Tue, 21 Aug 2007, Steve Faulkner wrote:
> 
> You seem to have "the wrong end of the stick" so to speak.

Possible. My appologies.


>> your needs were based on limitations of your accessibility tool
> 
> I myself do not require assistve technology to be able to access web 
> content, but I do advocate on behalf of those who do.

Oh. In that case, I encourage you to let them do their own talking. :-) If 
it turns out that actually nobody in the working group who actually wants 
to access this list is using ATs that don't work with Firefox, then there 
really is no point us supporting IE.


> > I wrote this tool over a weekend, mostly for fun, to help people see 
> > what the issues are. It doesn't work in IE because it uses 
> > standards-based features that IE doesn't support.
> 
> So i can help people hear what the issues are, can you tell me will i 
> need to modify all the JS files (onerror.js, utilities.js, and the in 
> page script) in order to make the scripts work with user agents that do 
> not support DOM3 Core?

I really have no idea. I would guess you'll have to look for uses of 
Node.textContent, which I know doesn't work in IE, but there might well be 
other issues as well.


> Also can i set up the pages remotely for development and testing?

Yeah; you'll just need some simple server-side shunts to proxy the CGI 
scripts, but other than that it should just work.


Philip Taylor has been working on a static version of the page, which 
might be of interest to you.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Tuesday, 21 August 2007 20:51:57 UTC