it think whats felts so off on scratchpad is sometimes people just want to
select dom elements like $('div'); on jquery to just check does it exist,
and in scratchpad this kind of command wont show anything. thanks Jshark to
mention it, i almost think that scratchpad broken when the first time i Run
it, have to write $('div').append('asdfsad') to see it in action.
maybe many people that build their working method with console.log() while
developing their web. this method building work flow like "talking" trough
console to what they work on (web page), and when we have to talk limited
in one line only, its feels off since in real code one liner is quite
savage :)
On Monday, December 5, 2016 at 9:27:11 PM UTC+7, Jshark wrote:
>
> I posted a bunch of my gripes on one of Honza's blog posts from late
> 2015. He suggested I file tickets in Bugzilla which, sorry to say, I never
> got around to. Life interferes, you know? Some have been addressed, these
> are the remaining ones I still find ... annoying. I realize that some/all
> of these might be "nope, it's the way dev tools works now", and if that's
> the case then I can accept it, but I might as well get my 2 cents in.
> Apologies if some of these have already been brought up.
>
> 1. debugger search. egads. #linenumber is engraved in my fingerprints.
> Finding something in the *current* file now needs a prefix (excuse
> me…”operator”)? What is that operator again? oh, wait, you can’t see those
> unless the search box is empty. I've managed to remember Ctrl-F most of
> the time, but I still find myself using "#" instead of ":" about 75% of
> the
> time to go to a line number.
> 2. The multi-line command window on the Console tab. Yes, scratchpad
> is kind of like that, but not really. It was nice having it on Console.
> 3. Back in high school you’d never hear me say this, but “I miss
> history”. Especially in the form of the Console Command Editor History
> menu. Yes, you can up-arrow through your history, but you don't see what
> that history actually is until you get there.
> 4. Remembering the source file you had open the last time you opened
> the debug window on this page.
> 5. Inspector Box Model tab – you can not edit the height/width of the
> inspected item as you used to be able to do in FB. Everything else, but
> not
> height &width.
>
> thx
> jeff
>
> On Wednesday, April 27, 2016 at 8:06:17 AM UTC-4, Sebastian Zartner wrote:
>>
>> The Firefox DevTools team is working on closing the gaps between their
>> tools and Firebug.
>> In the first quarter of the year the Firebug theme, HTTP log inspection
>> in the Console panel and the DOM panel were ported to Firefox (see bug
>> 1256749 <https://bugzilla.mozilla.org/show_bug.cgi?id=1256749>).
>>
>> Now the team is asking what should be fixed in Q2 2016. See bug 1267303
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1267303>.
>>
>> My suggestions:
>>
>> - 1004678 <https://bugzilla.mozilla.org/show_bug.cgi?id=1004678>:
>> Break on DOM mutation
>> - 1267144 <https://bugzilla.mozilla.org/show_bug.cgi?id=1267144>:
>> Allow to set breakpoints for XHRs
>> - 1165010 <https://bugzilla.mozilla.org/show_bug.cgi?id=1165010>: Set
>> a breakpoint for errors in WebConsole (like Firebug)
>> - 1226640 <https://bugzilla.mozilla.org/show_bug.cgi?id=1226640>: Add
>> Events side panel
>> - 1227054 <https://bugzilla.mozilla.org/show_bug.cgi?id=1227054>:
>> [rule view] Show whether a CSS property, value or selector is valid
>> - 1267140 <https://bugzilla.mozilla.org/show_bug.cgi?id=1267140>:
>> Allow auto-completing non-enumerable properties and member functions
>> return
>> types of known types
>>
>> (These are all existing issues, but you can also suggest issues that are
>> not already tracked in Bugzilla, of course.)
>>
>> Sebastian
>>
>
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to firebug+unsubscr...@googlegroups.com.
To post to this group, send email to firebug@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebug/03114caa-1402-4a26-b6c6-12671f88e1bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
