We want to support multi-line braille displays.
The library that talks to braille displays, brlapi, already has at least some support for multi-line, i.e. rows and columns.
The first step is just to keep track of the number of rows and columns separately, even if we don't populate them.
My suggestion is to start with the first line of code that takes the (rows, columns) from the braille display and turns it into a single cell count, and fix it to keep track of both rows and columns, then use the compiler to figure out what needs to change as a result of that.
Open chrome/browser/extensions/api/braille_display_private/brlapi_connection.cc and edit GetDisplaySize. Make it return rows and columns instead of just a size (see where it currently sets size to columns * rows).
Then try to compile Chrome and use the compile errors as a clue to figure out what to fix next.
At some point you will encounter braille_display_private.h and braille_display_private.cc, note that these are auto-generated from this file:
chrome/common/extensions/api/braille_display_private.idl
You will want to modify (long? textCellCount;) and replace it with rows and columns instead.
When you get all the way back to braille_display_manager.js, don't try to implement full support for multi-line, just use the number of columns instead of the total number of text cells.
The goal of this change is to update a bunch of data structures and make the code multi-line "aware", without actually changing any behavior for existing braille displays and without breaking anything.
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by dmazz...@chromium.org
, Sep 29 2016