@@ -1768,78 +1768,6 @@ <h2><a>FilterOptions</a> Dictionary</h2>
1768
1768
</ dl >
1769
1769
</ section >
1770
1770
1771
- <!--
1772
- <p class="issue">
1773
- It needs to be discussed whether to just allow using the above
1774
- messaging-specific MessagingFilter or otherwise to allow defining filters with
1775
- a generic syntax (as defined in the following sections) and reflect in this
1776
- specification on which attributes the implementation is required to filter in
1777
- an efficient manner (e.g. creating the corresponding indexes).
1778
- </p>
1779
-
1780
- <!------------------------ Interface CompositeFilter ------------------------->
1781
- <!--section>
1782
- <h2><a>CompositeFilter</a> Interface</h2>
1783
- <p>The <a>CompositeFilter</a> interface represents a filter that is the result
1784
- of combining several filters with an operator ('and' / 'or').
1785
- <dl title="interface CompositeFilter : AbstractFilter"
1786
- class="idl">
1787
- <dt>attribute AbstractFilter[] filters</dt>
1788
- <dd>The different filters that are combined in the composite
1789
- filter.</dd>
1790
-
1791
- <dt>attribute CompositeFilterOperator operator</dt>
1792
- <dd>Indicates the operator used to combined the different filters. It can
1793
- have the following possible values: 'and' and 'or'.</dd>
1794
- </dl>
1795
- </section>
1796
-
1797
-
1798
- <!------------------------ Interface AttributeFilter-------------------------->
1799
- <!--section>
1800
- <h2><a>AttributeFilter</a> Interface</h2>
1801
- <p>The <a>AttributeFilter</a> interface represents a filter of messages
1802
- based on the value of a specific attribute.
1803
- <dl title="interface AttributeFilter : AbstractFilter"
1804
- class="idl">
1805
- <dt>attribute DOMString filterBy</dt>
1806
- <dd>The attribute based on whose value the messages are filtered.</dd>
1807
-
1808
- <dt>attribute AttributeFilterOperator operator</dt>
1809
- <dd>Indicates the operator applied on the attribute indicated in the
1810
- <code>filterBy</code> parameter to filter the messages. It can have the
1811
- following possible values: 'is', 'contains', 'startswith', 'endswith',
1812
- 'exists'.</dd>
1813
-
1814
- <dt>attribute any filterValue</dt>
1815
- <dd>The value with which the attribute indicated in the
1816
- <code>filterBy</code> parameter is compared to filter the messages.</dd>
1817
- </dl>
1818
- </section>
1819
-
1820
-
1821
- <!------------------------ Interface AttributeRangeFilter -------------------->
1822
- <!--section>
1823
- <h2><a>AttributeRangeFilter</a> Interface</h2>
1824
- <p>The <a>AttributeRangeFilter</a> interface represents a filter of messages
1825
- with the value of a specific attribute within a range of values.
1826
- <dl title="interface AttributeRangeFilter : AbstractFilter"
1827
- class="idl">
1828
- <dt>attribute DOMString filterBy</dt>
1829
- <dd>The attribute based on whose value the messages are filtered.</dd>
1830
-
1831
- <dt>attribute any startValue</dt>
1832
- <dd>The minum value that the attribute indicated in the
1833
- <code>filterBy</code> parameter may have so that the corresponding message
1834
- is included in the result of this filter.</dd>
1835
-
1836
- <dt>attribute any endValue</dt>
1837
- <dd>The maximum value that the attribute indicated in the
1838
- <code>filterBy</code> parameter may have so that the corresponding message
1839
- si included in the result of this filter.</dd>
1840
- </dl>
1841
- </section>
1842
-
1843
1771
<!------------------------ Interface Enumerations ---------------------------->
1844
1772
< section >
1845
1773
< h2 > Enumerations</ h2 >
0 commit comments