Issue 4658 - Incorporate element hiding emulation filters

chrome/locale/en-US/global.properties

Index: chrome/locale/en-US/global.properties
===================================================================
--- a/chrome/locale/en-US/global.properties
+++ b/chrome/locale/en-US/global.properties
@@ -27,17 +27,17 @@
 remove_group_warning=Do you really want to remove this group?
 clearStats_warning=This will reset all filter hit statistics and disable counting filter hits. Do you want to proceed?
 
 filter_regexp_tooltip=This filter is either a regular expression or too short to be optimized. Too many of these filters might slow down your browsing.
 filter_unknown_option=Unknown filter option
 filter_invalid_regexp=Invalid regular expression
 filter_elemhide_duplicate_id=Only one ID of the element to be hidden can be specified
 filter_elemhide_nocriteria=No criteria specified to recognize the element to be hidden
-filter_cssproperty_nodomain=No active domain specified for CSS property filter
+filter_elemhideemulation_nodomain=No active domain specified for element hiding emulation filter

[Wladimir Palant, 2016/12/13 14:44:27]

This is a user-visible error message, do we really want users to know what
"element hiding emulation" is? How about "extended element hiding filter"?

[Felix Dahlke, 2016/12/13 15:55:39]

Done, although I went for "emulated element hiding filter" because I find
"extended element hiding filter" too ambiguous. I think "emulated element hiding
filter" is how we should call those when talking to filter list authors, because
that's really what they are: Element hiding filters that are not natively
supported and thus emulated.

[Wladimir Palant, 2016/12/13 16:33:03]

And "emulated" is not? As a user without knowledge of technical details, how are
you going to understand what is being emulated here and why these filters are
special? I still think that we need to call those "extended" and explain
everything further in the documentation.

[Felix Dahlke, 2016/12/13 17:07:48]

True, probably not that great either. I guess we'll have to think some more
about how to communicate this feature to users. But until then let's just go
with "extended", we can always change this error message later if we feel the
need to.

 
 subscription_invalid_location=Filter list location is neither a valid URL nor a valid file name.
 
 type_label_other=other
 type_label_script=script
 type_label_image=image
 type_label_stylesheet=stylesheet
 type_label_object=object