> There is no an explicit user action for this, but you can restart > Firefox or just disable/enable Firebug in Add-on Manager.
Funny, on my home pc this works just like that. I tried this at work several times but always had the old history items in there. Additionally I remember having read something about "survives browser sessions" or such but I can't find it anymore. I'll try again tomorrow and report.
>Why do you need to clear the history?
I just find it less confusing having just the important (current) items in there. But it's not a big thing, I mainly asked because I feared the history to get bigger and bigger if it stays alive between browser sessions.
In the Style tab of the HTML sidebar, relative paths in url() values are now apparently treated as relative to the page being viewed rather than the responsible CSS file. This can break Firebug's image tooltip, particularly on nested pages. I just switched from the 1.10 branch, so the issue may have been introduced before 1.11a6.
Oh, also, I reported this some time ago, but it may have slipped through the cracks, being so relatively minor: Under the Computed style tab on a Mac, disclosure triangles for each property group header are always stuck in the "closed" position, regardless of whether the group is expanded or collapsed. Those for properties themselves function as expected.
On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
> Thanks, guys! One issue I haven't seen mentioned:
> In the Style tab of the HTML sidebar, relative paths in url() values are > now apparently treated as relative to the page being viewed rather than the > responsible CSS file. This can break Firebug's image tooltip, particularly > on nested pages. I just switched from the 1.10 branch, so the issue may > have been introduced before 1.11a6.
Could you provide a test case for this?
> Oh, also, I reported this some time ago, but it may have slipped through > the cracks, being so relatively minor: Under the Computed style tab on a > Mac, disclosure triangles for each property group header are always stuck > in the "closed" position, regardless of whether the group is expanded or > collapsed. Those for properties themselves function as expected.
On Friday, November 9, 2012 9:01:49 AM UTC+1, Sebastian Zartner wrote:
> On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
>> Thanks, guys! One issue I haven't seen mentioned:
>> In the Style tab of the HTML sidebar, relative paths in url() values are >> now apparently treated as relative to the page being viewed rather than the >> responsible CSS file. This can break Firebug's image tooltip, particularly >> on nested pages. I just switched from the 1.10 branch, so the issue may >> have been introduced before 1.11a6.
On Friday, November 9, 2012 2:24:30 AM UTC-6, Sebastian Zartner wrote:
> On Friday, November 9, 2012 9:01:49 AM UTC+1, Sebastian Zartner wrote:
>> On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
>>> Thanks, guys! One issue I haven't seen mentioned:
>>> In the Style tab of the HTML sidebar, relative paths in url() values are >>> now apparently treated as relative to the page being viewed rather than the >>> responsible CSS file. This can break Firebug's image tooltip, particularly >>> on nested pages. I just switched from the 1.10 branch, so the issue may >>> have been introduced before 1.11a6.
On Friday, November 9, 2012 5:23:58 PM UTC+1, Siemova wrote:
> Thanks for the quick fixes, Sebastian! Much appreciated.
> - Siemova
> On Friday, November 9, 2012 2:24:30 AM UTC-6, Sebastian Zartner wrote:
>> On Friday, November 9, 2012 9:01:49 AM UTC+1, Sebastian Zartner wrote:
>>> On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
>>>> Thanks, guys! One issue I haven't seen mentioned:
>>>> In the Style tab of the HTML sidebar, relative paths in url() values >>>> are now apparently treated as relative to the page being viewed rather than >>>> the responsible CSS file. This can break Firebug's image tooltip, >>>> particularly on nested pages. I just switched from the 1.10 branch, so the >>>> issue may have been introduced before 1.11a6.
> On Friday, November 9, 2012 5:23:58 PM UTC+1, Siemova wrote:
>> Thanks for the quick fixes, Sebastian! Much appreciated.
>> - Siemova
>> On Friday, November 9, 2012 2:24:30 AM UTC-6, Sebastian Zartner wrote:
>>> On Friday, November 9, 2012 9:01:49 AM UTC+1, Sebastian Zartner wrote:
>>>> On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
>>>>> Thanks, guys! One issue I haven't seen mentioned:
>>>>> In the Style tab of the HTML sidebar, relative paths in url() values
>>>>> are now apparently treated as relative to the page being viewed rather than
>>>>> the responsible CSS file. This can break Firebug's image tooltip,
>>>>> particularly on nested pages. I just switched from the 1.10 branch, so the
>>>>> issue may have been introduced before 1.11a6.
>> --
> You received this message because you are subscribed to the Google
> Groups "Firebug" group.
> To post to this group, send email to firebug@googlegroups.com
> To unsubscribe from this group, send email to
> firebug+unsubscribe@googlegroups.com
> For more options, visit this group at
> https://groups.google.com/forum/#!forum/firebug
>> On Friday, November 9, 2012 5:23:58 PM UTC+1, Siemova wrote:
>>> Thanks for the quick fixes, Sebastian! Much appreciated.
>>> - Siemova
>>> On Friday, November 9, 2012 2:24:30 AM UTC-6, Sebastian Zartner wrote:
>>>> On Friday, November 9, 2012 9:01:49 AM UTC+1, Sebastian Zartner wrote:
>>>>> On Thursday, November 8, 2012 9:08:49 PM UTC+1, Siemova wrote:
>>>>>> Thanks, guys! One issue I haven't seen mentioned:
>>>>>> In the Style tab of the HTML sidebar, relative paths in url() values >>>>>> are now apparently treated as relative to the page being viewed rather than >>>>>> the responsible CSS file. This can break Firebug's image tooltip, >>>>>> particularly on nested pages. I just switched from the 1.10 branch, so the >>>>>> issue may have been introduced before 1.11a6.
>>> -- >> You received this message because you are subscribed to the Google >> Groups "Firebug" group. >> To post to this group, send email to fir...@googlegroups.com<javascript:> >> To unsubscribe from this group, send email to >> firebug+u...@googlegroups.com <javascript:> >> For more options, visit this group at >> https://groups.google.com/forum/#!forum/firebug
