On Monday, November 28, 2016 at 6:52:19 PM UTC+1, Nick Roosevelt wrote:
>
> I am dearly missing the feature that displayed json in a cookie in a nice 
> format.
>

That's already available, just displayed a bit differently than in Firebug:
 

<https://lh3.googleusercontent.com/-LMyvN07QtKQ/WEAwaz6FI-I/AAAAAAAAAnY/5x0KwGC4wNIFl9F6LXe245Xc5FYdXKUbgCLcB/s1600/Parsed%2BJSON%2Bvalue%2Bof%2Bcookie.png>

On Monday, November 28, 2016 at 6:52:19 PM UTC+1, Gregor Gonzalez wrote:
>
> But firebug was more of what I need, so fast compared with the problems I 
> face right now. 
>
>
>    - Now the inspector is a pain, sometimes doesn't work to choose an 
>    element, sometimes choose the element but only for 5 seconds and I have to 
>    search for it again.
>
> That sounds like a bug. You should file it with a reproducible test case 
<https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Inspector>.
 


>
>    - "Right click inspect with firebug" sometimes works, some times 
>    don't, sometimes show you the "body" and not the element you choosed. 
>
> The DevTools are slower than Firebug in this regard. (On my slow laptop 
this can take up to 5 to 10 seconds!) First the <body> element is selected, 
but later the inspected element is selected. Performance really needs to be 
improved.

>
>    - Adding tags, atributes, css, is more complicated and doesn't show 
>    live.
>
> CSS yes, HTML no. See bug 815464 
<https://bugzilla.mozilla.org/show_bug.cgi?id=815464> and bug 1067318 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1067318>.

Now: 
>
>    - Right click -> inspect (doesn't work)
>    - Right click -> inspect (Worked but does not show the element I 
>    choseed)
>
> If it's reproducible, please file a bug.

>
>    - Right click -> inspect (woked fine this time)
>    - I choose the elment to edit (cannot edit)
>    - Chose the atribute (cannot edit)
>
> Editing works by double-clicking (while in Firebug it works with a single 
click). 

>
>    - Chose the element again and "right click -> edit element"
>    - Show the entire node, search for the element inside. 
>    - I write to edit the element (nothing happens)
>    - Pressed enter (just create a new line)
>    - Deleted the line and re-write the atribute (because it created so 
>    many gaps and you have to clean manually)
>    - Enter doesn't work, so how you do: "ok make the changes"? I click 
>    there (doesn't work),  click on the page (doesn't work), click on the 
>    screen or menu (doesn't work).
>
> You need to press Ctrl+Enter or F2.

On Monday, November 28, 2016 at 6:52:20 PM UTC+1, joschka...@gmail.com 
wrote:
>
> I would rather see some small improvements like:
>
>
>    -     Jumping from one value to another in the BOX Model view (like in 
>    Firebug!)
>    
> Good UX suggestion! That should be covered by bug 1243045 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1243045>.

>
>    -     A real good syntax highlighting theme coz the new syntax 
>    highlighting is really bad (yes I know I now have my own chrome.css)
>
> If you have precise suggestions, you should report them 
<https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Style%20Editor>
.

>
>    -     Support copying the whole - absolute - CSS Selector path and not 
>    only the relative path (like in Firebug!)
>
> Like above, you should report a bug for it. Personally, I can't remember 
when I ever needed this option, so you should provide a good use case when 
filing it. 

>
>    -     A simple shortcut for the eyedropper
>
> Good point. That's bug 1177108 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1177108>. (Though that's 
unrelated to Firebug.)

>     
> and so on...
>
> I think that these suggestions are not so hard to implement, aren't they? 
> Please correct me if I'm wrong!
>

They do sound like easy things to implement. That said, I am not part of 
the DevTools team, so I can only forward suggestions. But I know that they 
welcome anyone who wants to contribute some code 
<https://wiki.mozilla.org/DevTools/GetInvolved>.

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/6617c049-0bee-48b3-b258-a3ec6406678a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to