This may depend on the SQL Developer version but, in fact, this does not work for any arbitrary string in view's DDL for the latest 4.0.3 production release.
And for an alternative, you can "roll your own" using techniques like those described below...
but using all_views.
Issue with SQL developer Version 18.104.22.168.
I've created a user report without employing additional tables or functions, using DBMS_METADATA.GET_DDL and ALL_VIEWS. It takes absurdly long to complete unless a schema is specified, though, and it isn't fast even if it is. It's sad that SQLDev can't do it on its own, while other tools can...
Here's report XML: http://pastebin.com/rMDrs4d9
It works, but not properly tested, so use at your own risk.
Thanks for your efforts. The difficulty here is that the Oracle DB and data dictionary do not provide a means to let us use pure SQL to search for text in the view source. The LONG data type, deprecated perhaps two decades ago, is a real thorn in the side. And, as you have seen, performance is always paramount when implementing a feature in a widely used tool like SQL Developer.
Here is a thoughtful post that describes the problem and some solutions using PL/SQL:
Recall that Find DB Object was completely rewritten for 4.0 and is vastly superior to the prior version (which also did not handle this case). Searching the view source for an arbitrary string is a remaining weakness that, given time, will probably get handled as an enhancement.