3

I'm writing a basic Chrome Extension to add suggestions in the Omnibox from a JSON feed. Nearly all queries entered will display results as expected in the suggestions dropdown.

However, it seems that whenever an ampersand (&) is returned as part of the description, Chrome throws an error.

The error thrown reads "xmlParseEntityRef: no name(...)" and is called from the parseOmniboxDescription method within Chrome.

Any help with this matter would be greatly appreciated. I'm not sure if this is the only character with that problem or if it is more widespread.

sdgluck
  • 24,894
  • 8
  • 75
  • 90
Tyler
  • 889
  • 1
  • 11
  • 17

1 Answers1

5

The current API for omnibox suggestions requires that they be specified as encoded XML text, not just plain text. Some characters including & will need to be appropriately encoded.

To encode an entire XML string in browser JavaScript, you may do something like this:

function encodeXml(s) {
  var holder = document.createElement('div');
  holder.textContent = s;
  return holder.innerHTML;
}

console.log(encodeXml("Good & Bad > Bad & Good"));
// "Good & Bad > Bad & Good"

If you perform this operation on your text before passing it to the omnibox API, the error should go away.

Per the documentation you can use <url>, <match>, and <dim> to further annotate your result. However, you may want to use a more structured XML-building approach for that, rather than simply concatenating strings. (I don't know if these XML elements have any attributes, but if they do, the approach above may not be adequate for encoding attribute values.)

Jeremy
  • 1
  • 85
  • 340
  • 366