opened
jonathanolson
username_0
Besides lineDash, it's generally a Scenery convention to have the default "no value" be `null`.

Currently, when checking to see if an accessibleOrder is set, we need to check the length (and zero-length is treated as "no order). Internally, we could definitely use a factored out hasAccessibleOrder function.

But client-side, does it make more sense (in order to clear an accessibleOrder) to have:
```js
node.accessibleOrder = null;
// or
node.accessibleOrder = [];
```

(using null technically creates fewer objects, but I believe unless this happens a LOT, it's probably in the noise and isn't worth worrying much about).

Thoughts?
Should null be the default accessibleOrder?
issue
created
zepumph
username_1
Seems fine to me either way. Setting it back to `null` to clear the options it is idiomatic to the `*tagName` options and how to clear that content from the PDOM.
comment
created
jessegreenberg
username_2
If `null` is supported, both
```js
node.accessibleOrder = null;
// and
node.accessibleOrder = [];
```
would be supported client-side, right? It seems fine to use that here. @username_0 if this change would fall nicely into the a11y-tree branch that is great, otherwise please re-assign to one of us to make the change.
comment
closed
jonathanolson
username_0
issue
created
jonathanolson
username_0
Implemented in the a11y-tree branch with the above commit. Presumably review will be included with the branch's review, closing here.
comment