Closed Bug 1228039 Opened 9 years ago Closed 6 years ago

Setup accessibility for B2GDroid

Categories

(B2GDroid Graveyard :: General, defect, P2)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sgiles, Assigned: sgiles)

References

Details

Attachments

(1 file)

Requires patch from bug 1224604
from bug 1224604:

(In reply to sgiles from comment #7)
> (In reply to Yura Zenevich [:yzen] from comment #6)
> > 
> > I'm trying a build with part 1+2 right now. Imidiate suggestion I have is to
> > separate mobile/android and mobile/android/b2gdroid so we would only load
> > correct presenters and resolve things in utils separately.
> 
> Yes, I was thinking grander, what if the b2gdroid chrome was able to
> register with AccessFu the presenters it required?  This would make new
> consumers of ./accessible much easier moving forward?

This is pretty interesting, looping in Eitan as well here.
Flags: needinfo?(eitan)
See Also: → 1228028
This is very cool indeed! I wonder how much of the accessibility module in the system app is needed for this to be good.
Flags: needinfo?(eitan)
Depends on: 1224606
Closing as we are not working on Firefox OS anymore.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: