Open Bug 1618403 Opened 5 years ago Updated 2 years ago

Consider not including nodeCssSelector into JSON tree view or making it optional.

Categories

(DevTools :: Accessibility Tools, enhancement, P5)

Product:
DevTools
Component:
Accessibility Tools
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: yzen, Unassigned)

Details

Looks like findCssSelector pretty heavy performance wise and eliminating that property might result in a speed up of an order of magnitude.

There hasn't been a lot of concern regarding the performance of Print to JSON functionality in the wild (though was mentioned by bgrienstead when he was trying to use a11y panel for some experiments) and it could be potentially added as a pref to panel settings. This would be a good bug that is slightly more work than a first bug.

Type: task → enhancement
Priority: -- → P4

Our bug handling documentation says:

P4
Do not use, this priority is for web platform test bots

Do we want p3 (backlog) or p5 (Will not fix, but will accept a patch) here?

Flags: needinfo?(yzenevich)

Yeah I guess P5 is more appropriate.

Flags: needinfo?(yzenevich)
Priority: P4 → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.