You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, is there a way to use the values of consultedNodes when calling computeAccessibleName or computeAccessibleDescription? Maybe we could add 2nd copies of those methods with different names that return an object { name/description: '...', consultedNodes: ... } to avoid breaking changes?
The text was updated successfully, but these errors were encountered:
I think this makes sense so that you can work around the current limitation for title attributes. We currently would consider the title for both name and description. With the new implementation we could initialize the consulted nodes for computeAccessibleDescription with the consulted nodes from computeAccessibleName.
Maybe we could add 2nd copies of those methods with different names that return an object { name/description: '...', consultedNodes: ... } to avoid breaking changes?
I'd rather make a breaking change than having to maintain two versions.
Hi, is there a way to use the values of consultedNodes when calling
computeAccessibleName
orcomputeAccessibleDescription
? Maybe we could add 2nd copies of those methods with different names that return an object{ name/description: '...', consultedNodes: ... }
to avoid breaking changes?The text was updated successfully, but these errors were encountered: