5 ms·

The main reason I don't switch to Firefox's dev tools is whenever i write a css attribute in the inspector, Chrome will present me a nice list of possible value

The main reason I don't switch to Firefox's dev tools is whenever i write a css attribute in the inspector, Chrome will present me a nice list of possible values I can choose, while Firefox just sits there patiently until I start writing. I don't always remember all the values and this really breaks my workflow.

Optimizer 13y ago
Firefox also provides a suggestions list for CSS properties and values in the rule view and the markup view of Inspector since Firefox 25.
- Ygg2 13y ago
  Actually I don't think it does for values. I just tried to 'change' the value of a font CSS property on Hacker News from Vedrana to something else and it didn't offer any font names.
  - evilpie 13y ago
    Well I guess that was kind of unlucky. clear, color etc. all work, it just can't do font suggestions.
  - talmand 13y ago
    What do you expect? Should it show every possible font you can type into the property? Just the fonts installed on your machine that other people may not have? Just any property that has a preset number of values show up as options as you type. The difference is that Chrome shows a dropdown list while with Firefox you have to sort of remember the values as it does an autocomplete. I see no reason Firefox couldn't offer the dropdown since it clearly knows the possible values. By the way, I tried the same font thing in Chrome and it responded the same way, no font list. You can see a similar behavior with color, for the value it shows possible colors by name. Start your color with # and suddenly there's no options. If there are too many possibilities to list it doesn't list anything.
    - deleted 13y ago
      [deleted]
    - deleted 13y ago
      [deleted]
Ygg2 13y ago
Good point, I was surprised it didn't work like that. Guess it's one of those little things. Personally, I think that console could do some work. Chrome console is top notch, and there is too much noise in FF version, with CSS and other stuff.
- dhenein 13y ago
  FWIW, you have pretty fine grained control over what appears in the console (CSS, JS, Logs, etc.) as well as the level of logging (Error, Warning, Log)... see the dropdown buttons at the top of the console tab :)
  - Ygg2 13y ago
    True, but default choice is SPAM WITH CSS REFLOWS, YAY! EDIT: Another thing, there needs to be a font shape difference between input and output. Basically, you should be able to tell if something is input or output without looking into the arrows to the side.
    - dhenein 13y ago
      I don't disagree :) Thanks for your feedback, I think determining sensible defaults for what to show in the console is a good discussion to have!
      - Ygg2 13y ago
        I just want Mozilla Firefox to be better :) What language are you guys writing Dev Tools? I'd love to be able to help out, but I'm not too great with C++?
        bgrins 13y ago
        It's mostly JavaScript. Take a look at https://wiki.mozilla.org/DevTools/GetInvolved https://wiki.mozilla.org/DevTools/GetInvolved and https://wiki.mozilla.org/DevTools/Hacking https://wiki.mozilla.org/DevTools/Hacking for more information

Optimizer 13y ago

Firefox also provides a suggestions list for CSS properties and values in the rule view and the markup view of Inspector since Firefox 25.

Ygg2 13y ago
Actually I don't think it does for values. I just tried to 'change' the value of a font CSS property on Hacker News from Vedrana to something else and it didn't offer any font names.
- evilpie 13y ago
  Well I guess that was kind of unlucky. clear, color etc. all work, it just can't do font suggestions.
- talmand 13y ago
  What do you expect? Should it show every possible font you can type into the property? Just the fonts installed on your machine that other people may not have? Just any property that has a preset number of values show up as options as you type. The difference is that Chrome shows a dropdown list while with Firefox you have to sort of remember the values as it does an autocomplete. I see no reason Firefox couldn't offer the dropdown since it clearly knows the possible values. By the way, I tried the same font thing in Chrome and it responded the same way, no font list. You can see a similar behavior with color, for the value it shows possible colors by name. Start your color with # and suddenly there's no options. If there are too many possibilities to list it doesn't list anything.
  - deleted 13y ago
    [deleted]
  - deleted 13y ago
    [deleted]

Ygg2 13y ago

Good point, I was surprised it didn't work like that. Guess it's one of those little things. Personally, I think that console could do some work. Chrome console is top notch, and there is too much noise in FF version, with CSS and other stuff.

dhenein 13y ago
FWIW, you have pretty fine grained control over what appears in the console (CSS, JS, Logs, etc.) as well as the level of logging (Error, Warning, Log)... see the dropdown buttons at the top of the console tab :)
- Ygg2 13y ago
  True, but default choice is SPAM WITH CSS REFLOWS, YAY! EDIT: Another thing, there needs to be a font shape difference between input and output. Basically, you should be able to tell if something is input or output without looking into the arrows to the side.
  - dhenein 13y ago
    I don't disagree :) Thanks for your feedback, I think determining sensible defaults for what to show in the console is a good discussion to have!
    - Ygg2 13y ago
      I just want Mozilla Firefox to be better :) What language are you guys writing Dev Tools? I'd love to be able to help out, but I'm not too great with C++?
      - bgrins 13y ago
        It's mostly JavaScript. Take a look at https://wiki.mozilla.org/DevTools/GetInvolved https://wiki.mozilla.org/DevTools/GetInvolved and https://wiki.mozilla.org/DevTools/Hacking https://wiki.mozilla.org/DevTools/Hacking for more information