Note that the live update issue is marked as one of the most important 
Firebug gaps <https://bugzilla.mozilla.org/show_bug.cgi?id=1267303#c11>.

Sebastian

On Thursday, May 4, 2017 at 2:09:09 PM UTC+2, Aleš Ulrych wrote:
>
> I'm sorry, I see you've already written about the live update. I will 
> read your instructions. Thanks for the help.
>
> Dne čtvrtek 4. května 2017 14:04:53 UTC+2 Aleš Ulrych napsal(a):
>>
>> Thanks for the instructions, it took me a moment to understand how it 
>> works now. However, I have to say that Firebug seems better to me. I 
>> very much miss the fact that when I edit (translate) HTML, Devtools does 
>> not show me immediate changes in the browser, as Firebug does. I always 
>> have to finish the edits, check them and then turn them on again, which 
>> makes me very reluctant. This could definitely improve. Meanwhile, I 
>> will stay with Firebug and Devtools will try out some other version.
>>
>> Dne čtvrtek 4. května 2017 13:24:45 UTC+2 Sebastian Zartner napsal(a):
>>>
>>> Within the Firefox DevTools you have similar options to edit the HTML. 
>>> You can edit attributes and text contents (and even tag names, which was 
>>> not possible in Firebug) by double-clicking them. To edit the whole HTML 
>>> structure under a specific element, right-click the element and choose 
>>> *Edit 
>>> As HTML* from the context menu. The only thing that's not yet working 
>>> is the live update of the website while typing, which is reported as bug 
>>> 1067318 <https://bugzilla.mozilla.org/show_bug.cgi?id=1067318> and bug 
>>> 815464 <https://bugzilla.mozilla.org/show_bug.cgi?id=815464>.
>>>
>>> Note that I have written a migration guide 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug> 
>>> explaining the most common questions for Firebug users. Please let me know 
>>> if you're missing something there. Furthermore, there is a bug report 
>>> covering all Firebug features that are currently missing in the DevTools 
>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=991806>. If you're 
>>> missing something that's not yet filed blocking that one (see the list 
>>> under "Depends on"), please file it and mark it as blocking bug 991806.
>>>
>>> Last but not least, I want to note that while the DevTools are still 
>>> missing some (important) features of Firebug and their UI is not as good as 
>>> Firebug's, they are in some areas already far more powerful than Firebug. 
>>> E.g. they have an Animations Editor 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Work_with_animations>,
>>>  
>>> they allow you to filter the CSS properties 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_CSS#Filtering_rules>,
>>>  
>>> they have a color picker 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Inspect_and_select_colors>
>>>  
>>> and different other CSS property helpers 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Visualize_transforms>,
>>>  
>>> and they allow to inspect the fonts used within an element 
>>> <https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/View_fonts#Fonts_view>,
>>>  
>>> to name just a few of their features.
>>>
>>> Sebastian
>>>
>>> On Thursday, May 4, 2017 at 11:16:11 AM UTC+2, Aleš Ulrych wrote:
>>>>
>>>> Thanks for the info, I thought it was just some cut Firebug. I also 
>>>> use Firebug as a helper for translating a German web-based e-shop when I 
>>>> receive an HTML code. Just leave me a blank page open in Firefox, turn 
>>>> on Firebug, choose to edit and insert HTML code there, and right now in 
>>>> Firefox I can see what it contains (bullets, tables, headings ... 
>>>> including 
>>>> properly translated HTML entities). I have an overview and very easy 
>>>> to translate. Then I copy the HTML code and return it back to the 
>>>> customer. With Firefox Devtools, I have no option to edit the HTML 
>>>> code to make it look the same as Firebug. The only solution for me is 
>>>> to turn off the E10s yet. :(
>>>> Is support planned?
>>>>
>>>> Dne středa 3. května 2017 22:47:11 UTC+2 Sebastian Zartner napsal(a):
>>>>>
>>>>> When e10s is enabled, the Firefox DevTools are opened instead of 
>>>>> Firebug, because Firebug does not work with e10s 
>>>>> <https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/>.
>>>>>  
>>>>> Those tools have the HTML ancestor path is at the bottom of the panel.
>>>>>
>>>>> Sebastian
>>>>>
>>>>> On Wednesday, May 3, 2017 at 2:47:53 PM UTC+2, Aleš Ulrych wrote:
>>>>>>
>>>>>> Here is Firebug with disabled e10s
>>>>>>
>>>>>>
>>>>>> Dne středa 3. května 2017 13:55:59 UTC+2 Aleš Ulrych napsal(a):
>>>>>>>
>>>>>>> Hello,
>>>>>>> I have a problem. When I have Electrolysis (e10) turned on in 
>>>>>>> Firefox,
>>>>>>> The HTML menu in Firebug I'm actively using will disappear. I did 
>>>>>>> not come up with it,
>>>>>>> How to turn it back on when electrolysis is turned on.
>>>>>>>
>>>>>>>

-- 
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/69264e9c-fc82-4b4e-82e1-9116e122ea02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to