Firing selectionchange on disconnected elements would require a different code path, as it currently depends on `nsTextControlFrame` which is only available when connected to a tree. Maybe it could make sense to not fire an event for comment #1 case, but I think it should fire one for comment #0 case. Setters probably can force a layout flush to get a frame in that case. What do you think, Masayuki?
Bug 1675894 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Firing selectionchange on disconnected elements would require a different code path, as it currently depends on `nsTextControlFrame` which is only available when connected to a tree. Maybe it could make sense to not fire an event for comment #1 case, but I think it should fire one for comment #0 case. Setters probably can flush layout to get a frame in that case. What do you think, Masayuki?
Firing selectionchange on disconnected elements would require a different code path, as it currently depends on `nsTextControlFrame` which is only available when connected to a tree. Maybe it could make sense to not fire an event for comment #1 case, but I think it should fire one for comment #0 case. Setters probably can flush layout to get a frame in that case (only when NODE_NEEDS_FRAME is set, to prevent performance degradation?). What do you think, Masayuki?