搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

sass debuginfo?

  • 4 回覆
  • 1 有這個問題
  • 13 次檢視
  • 最近回覆由 guigs

more options

I'm sure that one or two people still use firebug. Please could you inform me as what may have changed in the source to alter the interpretation of debug info additions? I realise that firebug is not your baby, and that source maps are the coming (extant?) thing, but any advice would be appreciated. JS

I'm sure that one or two people still use firebug. Please could you inform me as what may have changed in the source to alter the interpretation of debug info additions? I realise that firebug is not your baby, and that source maps are the coming (extant?) thing, but any advice would be appreciated. JS

所有回覆 (4)

more options

Check out the Firebug issue page on the fist link under the list of extensions here: http://getfirebug.com/wiki/index.php/Firebug_Extensions

more options

Thanks for the reply, but I couldn't find anything there other than a form to fill in. Was that what you had in mind?

more options

The intention was to put you in contact with the working team for Firebug to ask if there have been any changes. All of their documentation is also located on that Wikipedia page. The last change that I can find is on the Road Map for back in June This is also the first time there is a question about Firebug, as it is not a specialized topic in the forum.

It also looks like they have release notes: https://getfirebug.com/firstrun#Firebug%202.0.4. On the irc channel #firebug I have also pointed them to your question, so I am hoping to get more information.

more options

Ah! I got some info, there does not seem to be any changes in Firebug in regards to Sass, however I have been informed that the sass project is moving to use source maps instead of debug-info. It was also recommended to try the FireSass extenstion. http://getfirebug.com/wiki/index.php/Firebug_Extensions#FireSass


Check out also: Live Editing Sass and Less in the Firefox Developer Tools on the Mozilla Blog Is this still the case for you?