Firebug shortcuts conflict with build-in DevTools' ones

The Firebug users are currently experiencing some shortcut conflicts related to the built-in DevTools. Namely this is the inspector shortcut Ctrl+Shift+C. We (the Firebug Working Group) are trying to fix this[1] by disabling the shortcut. Because it's lazy loaded we can't access it immediately.

Re: Firebug shortcuts conflict with build-in DevTools' ones

3, 2013 at 7:43 AM, Sebastian Zartner wrote: The Firebug users are currently experiencing some shortcut conflicts related to the built-in DevTools. Namely this is the inspector shortcut Ctrl+Shift+C. We (the Firebug Working Group) are trying to fix this[1] by disabling the shortcut

Re: Intent to ship: vertical text support (CSS writing-mode and related properties)

CSS Logical Properties Level 1 doesn't even in WD status yet. Therefore I assume everything in there can still change fundamentally. So are you sure logical properties should be shipped already? Could the writing mode features perhaps be shipped independently from the logical properties? This is

Re: Searchfox (new code search tool)

On 7 June 2016 at 07:18, Mike Hommey wrote: > MXR is already taking too long to fade out of existence, do we really > want yet another different tool? For some contributors (like me) this may be, because they simply don't know that DXR is meant to replace MXR. If you want

Re: Intent to make Form Autocomplete popups use richlistbox's instead of trees

Hi Mike, I'm not much into that topic, though I'm wondering why you don't try to switch to HTML already as the DevTools team started to do[1] recently. Sebastian [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1263750 On 19 August 2016 at 17:25, Mike Conley wrote: >

Re: Some recent crash-stats improvements

On 11 October 2016 at 05:41, Nicholas Nethercote wrote: > On Tue, Oct 11, 2016 at 5:17 AM, Peter Bengtsson > wrote: > > > > If indeed, the memory report is safe to always show I'll change the > template > > to always show the memory_report link

CSS roadmap for 2020

Hi everybody, 2020 is already about two weeks old now and I stumbled over the list of planned CSS features again at https://wiki.mozilla.org/CSS. As the list is totally outdated, I was wondering what are the plans for CSS for this year? Is there some place where users can get involved in the

Re: CSS roadmap for 2020

On Thu, 16 Jan 2020 at 21:59, Sean Voisen wrote: > On Thu, Jan 16, 2020 at 7:50 AM Sebastian Zartner < > sebastianzart...@gmail.com> wrote: > >> Hi everybody, >> >> 2020 is already about two weeks old now and I stumbled over the list of >> planned CSS fea

Re: Intent to implement: CSS conic-gradient

On Monday, February 17, 2020 at 9:31:58 AM UTC+1, Patrick Brosset wrote: > Thanks Tim, this is very exciting! > > Regarding DevTools: you are right, having an editor would be great and the > same is true for other kinds of gradients. Here's a bug for a > linear-gradient editor for reference: >

Re: Intent to prototype: Allow :is() and :where() to have better selector error recovery.

On Monday, September 14, 2020 at 12:24:13 AM UTC+2, Emilio Cobos Álvarez wrote: > DevTools bug: I'm not sure if it is necessary to have a devtools bug for > this. The selector will serialize as :is(div) rather than :is(div, > :nonsense), for example. Other than that, devtools should just work.

Re: Experimental Features in about:preferences

I'd like to point out that there is also an MDN page listing experimental features: https://developer.mozilla.org/docs/Mozilla/Firefox/Experimental_features Maybe that page could be linked to from the new section? And maybe other features listed there could be added to the section? Best

Re: PSA (Windows): Startup Skeleton UI Enabled on Nightly

On Wednesday, January 6, 2021 at 10:55:22 PM UTC+1, Doug Thayer wrote: > On 1/6/2021 1:51 PM, Mike Hommey wrote: > > > On Wed, Jan 06, 2021 at 01:46:52PM -0800, Doug Thayer wrote: > >> On 1/6/2021 1:44 PM, Mike Hommey wrote: > >> > >>> On Wed, Jan 06, 2021 at 01:30:00PM -0800, Doug Thayer

Re: PSA (Windows): Startup Skeleton UI Enabled on Nightly

On Thursday, January 7, 2021 at 7:07:05 PM UTC+1, Doug Thayer wrote: > On 1/7/2021 4:18 AM, Sebastian Zartner wrote: > > > On Wednesday, January 6, 2021 at 10:55:22 PM UTC+1, Doug Thayer wrote: > >> On 1/6/2021 1:51 PM, Mike Hommey wrote: > >> > >>>

Re: Intent to prototype: glyph-scale-factor descriptor for @font-face rules

On Monday, March 15, 2021 at 1:39:36 PM UTC+1, Jonathan Kew wrote: > Summary: For a given "font size" as expressed e.g. in CSS px or points, > different fonts can vary significantly in how visually large they look. > The nominal "font size" does not necessarily relate to any specific >