[gtk+] Mention type vs region ambiguity in the docs

[Matthias Clasen <matthiasc src gnome org>]

commit 0a5e8ce685ea2c41bf78bd059d2611f2355dceef
Author: Matthias Clasen <mclasen redhat com>
Date:   Wed Jan 19 12:55:48 2011 -0500

    Mention type vs region ambiguity in the docs

 gtk/gtkcssprovider.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)
---
diff --git a/gtk/gtkcssprovider.c b/gtk/gtkcssprovider.c
index ea4530e..32d637e 100644
--- a/gtk/gtkcssprovider.c
+++ b/gtk/gtkcssprovider.c
@@ -157,6 +157,12 @@
  * style classes they define and see <xref linkend="gtkstylecontext-classes"/>
  * for a list of all style classes used by GTK+ widgets.
  * </para>
+ * <para>
+ * Note that there is some ambiguity in the selector syntax when it comes
+ * to differentiation widget class names from regions. GTK+ currently treats
+ * a string as a widget class name if it contains any uppercase characters
+ * (which should work for more widgets with names like GtkLabel).
+ * </para>
  * <example>
  * <title>Style classes in selectors</title>
  * <programlisting language="text">
@@ -1718,7 +1724,8 @@ is_widget_class_name (const gchar *str)
    * widget class names contain only CamelCase
    * (gtkmm widgets don't), but at least part of
    * the name will be CamelCase, so check for
-   * the first uppercase char */
+   * the first uppercase char
+   */
   while (*str)
     {
       if (g_ascii_isupper (*str))