Willie: > Are you suggesting that WebKit not integrate in Solaris until it is > more fully accessible? If so, what do you recommend be done instead?
I notice that you raised this issue in the thread "Who is using WebKit in GNOME 2.28" on the GNOME desktop-devel-list at gnome.org. From that discussion it sounds like yelp will not be using it in the 2.28 timeframe, but will likely switch to WebKit for GNOME 2.30. Other programs which use it are devhelp, epiphany, and seed. Is that a complete list? Of these, we only ship devhelp. Not sure about the plans for devhelp, or how important a11y support in devhelp is, so it would be good to get clarification about that. The main reason for integrating WebKit is so that it can be embedded in programs like yelp and devhelp. If WebKit is not usably accessible, then we can continue to deliver older versions of the yelp and devhelp modules which do not use WebKit and not lose any accessibility. That said, I do not think this needs to impact whether we deliver WebKit. When the Desktop team first delivered Firefox and Thunderbird they were also not usably accessible and it took some time for the upstream communities to address this. We can choose to deliver WebKit and also choose not to use it in programs like yelp and devkit if lack of accessibility is an issue for yelp and/or devkit. So, would it be acceptable to separate these two issues? We can approve WebKit for integration and then have a future case which will seek approval for making use of it in programs like yelp and devkit. Perhaps this could be addressed in the upcoming GNOME 2.28 Umbrella case. Would that be agreeable? At any rate, this case is due to time-out tomorrow, and this is the only remaining open issue. Do you think it will be possible to wrap up this issue by then, or do we need to further extend the timeout? Brian
