Issue with 1Password Browser Extension Not Searching Note Fields

+1 At minimum, the search functionality should not have discrepancies in behavior among platforms unless the particular platform dictates this change. And if it does, ideally the UI will indicate the difference when it becomes apparent that the user is possibly trying to use a feature that is exclusive to another platform.

When implementing this feature I think the order of the displayed search results should be influenced by the field that said result was found in. i.e. A hit in the Title is returned above URL which is above notes etc. 

Also, I wanted to make a distinction between the notes field on any item and a secure note. I think these should be treated differently. Or at least have the option to do so. Maybe there should be a plain text "notes" field that is searchable and a distinct "secure notes" (or maybe "protected notes"?) field that can be added to any item which would allow a masked notes field that would have to be revealed to see the contents and would therefore not be searchable just like a password field is today. 

Now that I think about it, rather than a separate field, maybe any field should have the option to be "protected" so that it is by default masked, must be manually revealed and would not be returned in search results. You could even optionally require reauthentication to reveal the contents.