Yep. I think the request has come up before, but it would require a quite large refactoring. The search logic currently does a recursive traversal and searches against all possible parts (tag name, attribute name, attribute value).
Possibly we could add a hack so that the precise case "<form" worked, but "<form>", "<form attr", etc. are hard. But note that focus is on https://github.com/firebug/firebug.next/ at the moment. Den lördagen den 20:e september 2014 kl. 01:19:50 UTC+2 skrev David H: > > I had a funky WordPress page that apparently had two <form tags in it when > we only wanted one so I opened it up in Firebug to the HTML tab, clicked > into that text area, then hit Ctrl+F and search for <form, but the field > turned red and I got the error beep which indicated there were no results > found. I searched for form instead and it found them... just none of the > <form instances even though I was looking at one of them. > > See screenshot. I'm not sure how to explain this unless the actual code is > formatted differently in which case Firebug should ignore that because I'm > searching within the context of its formatted code. > -- 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/789a8713-28fa-40db-9512-2b1407534fa3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
