Open
Bug 1379275
Opened 7 years ago
Updated 2 years ago
Selectboxes/dropdowns in servicenow are laggy/difficult to use when dom.forms.select.customstyling is enabled
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
People
(Reporter: jen, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf, perf:responsiveness, testcase-wanted)
Attachments
(1 file)
18.38 KB,
image/png
|
Details |
When trying to select a value in a drop down in Service Now, the drop down is slow to display and control. It will often open and close and not allow me to choose an option from the list. I often have to get around this by using my down arrow on my keyboard to select the value.
Comment 1•7 years ago
|
||
Could you provide steps to get to one of these dropdowns? The selectboxes I get in, say, https://mozilla.service-now.com/sp?id=sc_cat_item&sys_id=e3b696fe0fc66600f67ab65be1050e96 , look different, but I don't know how to get to the page in your screenshot (and even if I could, with whatever privileges I get on service-now (not really any, AFAICT! :-) ). Do we have control over the servicenow vendor / software? Does it work better in another browser (Edge/Chrome/Safari) ?
Component: General → Untriaged
Flags: needinfo?(jhayashi)
Summary: Drop down menus are difficult to use → (Pseudo?)selectboxes/dropdowns in servicenow are difficult to use
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to :Gijs from comment #1) > Could you provide steps to get to one of these dropdowns? The selectboxes I > get in, say, > https://mozilla.service-now.com/ > sp?id=sc_cat_item&sys_id=e3b696fe0fc66600f67ab65be1050e96 , look different, > but I don't know how to get to the page in your screenshot (and even if I > could, with whatever privileges I get on service-now (not really any, > AFAICT! :-) ). The dropdowns are in the fullfiller view - to which I don't think you have access, but i can give you access in our dev server. > > Do we have control over the servicenow vendor / software? Does it work > better in another browser (Edge/Chrome/Safari) ? We have some control, but that's dropdown is core feature and we don't have much control over it. The same drop down behaves correctly in Chrome and Safari.
Flags: needinfo?(jhayashi)
Comment 3•7 years ago
|
||
(In reply to Jennifer Hayashi [:jen] from comment #2) > The same drop down behaves correctly in Chrome and > Safari. OK. Does it work in Firefox release (I'm assuming you're using Nightly)? If so, could you use mozregression ( https://mozilla.github.io/mozregression/ ) to narrow down when it broke?
Flags: needinfo?(jhayashi)
Reporter | ||
Comment 4•7 years ago
|
||
(In reply to :Gijs from comment #3) > (In reply to Jennifer Hayashi [:jen] from comment #2) > > The same drop down behaves correctly in Chrome and > > Safari. > > OK. Does it work in Firefox release (I'm assuming you're using Nightly)? If > so, could you use mozregression ( https://mozilla.github.io/mozregression/ ) > to narrow down when it broke? I am using nightly on a Macbook - OS 10.11.6. I tried in FF54, and there's similar behavior, but the lag and inability to control is more pronounced in Nightly. I tried to install the mozregression, but I seem to have all kind of errors.
Flags: needinfo?(jhayashi)
Reporter | ||
Comment 5•7 years ago
|
||
Not sure if this matters, but my coworker is on OS 10.12 and he's experiencing the same issue but his is less noticeable than on my machine. In his FF54 - it's barely noticeable.
Comment 6•7 years ago
|
||
Out of curiosity, if you go to about:config and flip dom.forms.select.customstyling to false, and restart Firefox, does the problem lessen?
Flags: needinfo?(jhayashi)
Reporter | ||
Comment 7•7 years ago
|
||
(In reply to Mike Conley (:mconley) - Digging out of needinfo / review backlog. from comment #6) > Out of curiosity, if you go to about:config and flip > dom.forms.select.customstyling to false, and restart Firefox, does the > problem lessen? Yay! - updated that to false, and it does make it much better. There's still a little bit of a lag, but it's not frustrating like it was before.
Flags: needinfo?(jhayashi)
Updated•7 years ago
|
Updated•7 years ago
|
Summary: (Pseudo?)selectboxes/dropdowns in servicenow are difficult to use → Selectboxes/dropdowns in servicenow are laggy/difficult to use when dom.forms.select.customstyling is enabled
Updated•7 years ago
|
Priority: -- → P3
Comment 8•7 years ago
|
||
Doesn't sound like this is critical enough that we'd take a late-breaking fix for it on 57beta (particularly since its severity is variable, per comment 5). --> firefox57:wontfix And ideally, we need to come up with a testcase (or some generally-accessible page) before we can usefully proceed here, I think... --> testcase-wanted
Keywords: perf,
testcase-wanted
Updated•7 years ago
|
status-firefox57:
--- → wontfix
Comment 9•5 years ago
|
||
If this is still reproducible, can we get a Gecko Profile of this case?
Flags: needinfo?(jhayashi)
Whiteboard: [qf:p3:responsiveness]
Comment 11•5 years ago
|
||
Install the addon from https://profiler.firefox.com/
ctrl-shift-1 will start profiling, ctrl-shift-2 will capture it. You then need to Publish it (you can redact URLs/etc if you wish/need to).
Updated•2 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•