Hi Brian: Brian Cameron wrote: >> 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.
Yep - I raised it there as a means to help us determine what we need to do for accessibility on the OpenSolaris desktop. > 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 list came from the GNOME release team and was based upon jhbuild dependencies: http://mail.gnome.org/archives/desktop-devel-list/2009-August/msg00275.html I've no idea if it is complete or not, but I suspect it is. > 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. Agreed. There are two purposes for this discussion. The first is to recognize that WebKit is not a shoe-in for a11y. I think this needs to be recorded in the ARC case and we need to track some sort of get well plan. The second is to understand the impact of shipping WebKit without a good a11y implementation. Given that yelp will likely stick with Gecko, the main touchpoint/intersection with OpenSolaris for 2.28 seems to be devhelp, and I believe that's probably OK. > 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? Yep! > 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? I think we're good to go. In addition, my ideal for the GNOME community would be that it's OK to develop against WebKit with a future goal of migrating to it, but that the default switches for GNOME modules should ensure that GNOME provides an accessible solution. With that, the upstream stuff in GNOME will cause fewer special-cases and issues downstream in OpenSolaris. Will
