Autocomplete and words beginning with dot (.)

I see, the main issue then is if in the URL the term can pass with the dot and without breaking the URL.
Some scape char like \ ?
Then in the JS add the \ if the term begins with .
That would require some major changes in the autocomplete callback as well.
Should I try that?

Thanks,
Ricardo.

I agree, but we can think of an autocomplete enhancement.
I think it should have something like: autocomplete_path?key=QueryString.
And for the sake of backwards compatibility: autocomplete_path/QueryString?key=QueryString.

And of course the new callbacks can use the QueryString on the path like they used to, or the key in the querystring.

Of course, the breaking of the URL still has to be taken into account.

The team tester found this breaking term: word/.net which also breaks the URL.

I created this two patches for the project running Drupal 7.14.

The revision 35 being the Drupal stable.

What do think about this?

Index: autocomplete.js
===================================================================
--- autocomplete.js	(revisión: 35)
+++ autocomplete.js	(revisión: 73)
@@ -270,6 +270,13 @@
 
   // See if this string needs to be searched for anyway.
   searchString = searchString.replace(/^\s+|\s+$/, '');
+  
+  originalSearchString = searchString;
+  // See if this string begins with dot
+  searchString = searchString.replace(/^\./, '');
+  searchString = searchString.replace('/.', '');
+  db.searchString = searchString;
+  
   if (searchString.length <= 0 ||
     searchString.charAt(searchString.length - 1) == ',') {
     return;
@@ -292,6 +299,7 @@
     $.ajax({
       type: 'GET',
       url: db.uri + '/' + Drupal.encodePath(searchString),
+      data: {search_string: originalSearchString},
       dataType: 'json',
       success: function (matches) {
         if (typeof matches.status == 'undefined' || matches.status != 0) {

And in the taxonomy module:

Index: taxonomy.pages.inc
===================================================================
--- taxonomy.pages.inc	(revisión: 35)
+++ taxonomy.pages.inc	(revisión: 73)
@@ -108,12 +108,19 @@
  * @see taxonomy_field_widget_info()
  */
 function taxonomy_autocomplete($field_name, $tags_typed = '') {
-  // If the request has a '/' in the search text, then the menu system will have
-  // split it into multiple arguments, recover the intended $tags_typed.
-  $args = func_get_args();
-  // Shift off the $field_name argument.
-  array_shift($args);
-  $tags_typed = implode('/', $args);
+  
+  // First look for the search_string via $_GET
+  if(!empty($_GET['search_string'])){
+    $tags_typed = $_GET['search_string'];
+  }else{
+    // If the request has a '/' in the search text, then the menu system will have
+    // split it into multiple arguments, recover the intended $tags_typed.
+    $args = func_get_args();
+    // Shift off the $field_name argument.
+    array_shift($args);
+    $tags_typed = implode('/', $args);
+  }
+  
 
   // Make sure the field exists and is a taxonomy field.
   if (!($field = field_info_field($field_name)) || $field['type'] !== 'taxonomy_term_reference') {

Attaching a patch, see if it's good enough.

If that gets fixed, the patch here only would be a change in the behavior of the autocomplete, adding a search_string as a parameter, then modules like taxonomy catch the search string as a parameter.

And yes! it should be the symfony2's request(). But didn't know about the Request until @droplet pointed out.

Sorry, don't know Symfony that much. Time to learn new stuff!!