Open Bug 1850486 Opened 2 years ago Updated 1 year ago

devtools - make enter / tab autocomplete CSS value without going to next property

Categories

(DevTools :: Inspector: Rules, enhancement, P3)

Firefox 117
enhancement

Tracking

(Not tracked)

People

(Reporter: juraj.masiar, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

The autocomplete for the CSS functions in the dev-tools is currently not very user friendly.
STR: see the attached video or do this:

  1. write "filter" + Enter (or Tab)
  2. write "hue" + Enter (or Tab)

Actual results:

Invalid style is auto-completed:

filter: hue-rotate;

Expected results:

filter: hue-rotate(<place_cursor_here>);

Currently both Tab and Enter keys will wrongly autocomplete function name without parameters or parentheses, thus creating invalid style.
The workarounds are:

  • write whole function name without autocomplete
  • press RIGHT arrow key (not reachable by any finger without moving your hand)

This would help A LOT, thank you :)

Moving this to DevTools > Inspector component to allow our engineers to examine it more closely. If this is not the right component, please move it to a more appropriate one. Thanks!

Component: Untriaged → Inspector
Product: Firefox → DevTools

thanks for filing, overall it makes sense to avoid jumping to the next property if you are using an autocomplete on a value in the ruleview

Status: UNCONFIRMED → NEW
Component: Inspector → Inspector: Rules
Ever confirmed: true
Priority: -- → P3
Summary: devtools - make enter / tab autocomplete CSS function name → devtools - make enter / tab autocomplete CSS value without going to next property
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: