Open efficientbaxter opened 9 years ago
It looks like they search against the name of the feature and the description. In my mind, it really should only match the name as it does now. I'm willing to be argued with of course.
On Sun, Apr 19, 2015 at 5:35 PM, efficientbaxter notifications@github.com wrote:
If I query for @supports https://github.com/supports it says nothing found, if I query for supports only CSS.supports() API is found, none of the other results shown on http://caniuse.com/#search=supports
— Reply to this email directly or view it on GitHub https://github.com/cfjedimaster/brackets-caniuse/issues/15.
Raymond Camden, Developer Advocate for MobileFirst at IBM
Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden
Well, @supports
isn't the only case here. A lot of times I personally search just for a property, without knowing (and honestly, mostly not even caring) how the feature is called in the spec (or on canuise for that matter).
Maybe just make it optional? A checkbox under the searchbox would suffice I think since most of the space there is unused anway (since the result window is higher in most cases).
I would really like to see this as well
Checkbox sounds like a good idea. Want to build it? ;)
I've updated it to search against the description. Please check it out.
If I query for @supports it says nothing found, if I query for supports only CSS.supports() API is found, none of the other results shown on http://caniuse.com/#search=supports