Thanks for the hint, Simon! I totally forgot about that again. Tony, if you want to try it out, you can download the latest alpha here:
https://getfirebug.com/releases/firebug/1.13/ Sebastian On Thursday, December 19, 2013 6:10:10 PM UTC+1, Simon Lindholm wrote: > > As yet another, perhaps more user-friendly, option: in Firebug 1.13 alphas > you can find elements that match xpath selectors through the HTML panel > search field. > > Den torsdagen den 19:e december 2013 kl. 00:39:05 UTC+1 skrev Sebastian > Zartner: >> >> I noticed once when I clicked on Firebug console that it said "enabling >>> this causes a firefox stop or slowdown or something". I can't get this >>> warning again. It is not showing up. I must have accidentally cleared it. >>> >> I assume you're talking about this message: >> >> *Warning:* Enabling the Script panel causes a Firefox slow-down due to a >> platform >> bug <https://bugzilla.mozilla.org/show_bug.cgi?id=815603>. This will be >> fixed with the next major Firefox and Firebug versions. >> >> So if you don't need the Script panel, just disable it. >> >> Besides that showing strict warnings also can cause some slow-down. To >> disable displaying strict warnings, you can uncheck the equally named >> option within the Console panel options <http://goog_540211844>. >> >> So my question: is there a problem running firebug, firefox and selenium >>> IDE? There is for me. Is it due to this error above or some other >>> reason? What can I do about it? I need Selenium IDE only to test XPATHs. >>> True, Firebug has an xpath tester but it is very unreliable and quite >>> often, testing an xpath does nothing (shows nothing found but also shows no >>> errors and does not say "no matches found"). >>> >> If you just want to test XPaths, you really don't need Selenium IDE. >> In Firebug there are two ways to test XPaths. One is the integrated >> $xcommand<https://getfirebug.com/wiki/index.php/$x>, >> which returns different types of results depending on the XPath you are >> testing. And for advanced testing you can use the extension >> FirePath<https://getfirebug.com/wiki/index.php/Firebug_Extensions#FirePath>, >> which selects matching elements within an HTML view and inside the page. >> Results, which don't return elements are shown within its panel. And if >> there are no matches, there's a hint at the bottom telling you so. >> So if you think one of those two functionalities is "very unreliable", >> please let us (in case of the $x command) or the FirePath authors know >> what's wrong and provide a little test case, so your problem can be >> reproduced. >> >> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/f092d41c-63eb-4679-ab33-85c2737b2842%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
