Asanka Herath

This doesn't happen all the time and is only an issue when the optimistic symbol mapping code fails. We need something much more robust than what we have now.

Due to platform specific signatures, there could be multiple matches in a xref search. Need a way to squash those into a single xrefnode.

The backend can return platform specific signatures in response to `xref_search`. These signatures don't show up in an `annotation_request` for the same file. This breaks `GetDisplayName()`.

Make it possible to pull in vim-codesearch via chromium/src/tools/vim

1

Let it be possible to pull in the plugin via something like: ``` viml so `=path_to_chrome . 'tools/vim/vim-codesearch.vim'` ```

Inclusion of the `version` field in algorithm 5.2.1 carries the risk of a platform unwittingly allowing that field to be used as an identifier. Let's remove that from the spec,...

Consider a blocklist for schemes instead of a safelist

22

Mostly passing along some of the comments from [this Blink Intent-to-implement](https://groups.google.com/a/chromium.org/d/msg/blink-dev/29sFh4tTdcs/K4XroilVBAAJ). The use of a safelist presents a challenge to someone introducing a new protocol who wishes to integrates it...

Allow configuring Pandoc

18

Add Pandoc configuration options for those situations where `--mathjax` alone doesn't cut it.