diff options
| author | ahernandez.miralles@gmail.com <ahernandez.miralles@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-16 23:38:30 +0000 |
|---|---|---|
| committer | ahernandez.miralles@gmail.com <ahernandez.miralles@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-16 23:38:30 +0000 |
| commit | 5748a5989bf673d62d99fd399e39f263f7982bea (patch) | |
| tree | 27d3788cdabf4cc938cdf0923011dfb158d5ac5f /extensions/test | |
| parent | 83fb2a9e5fdfd7cc90928a4fd1a280eff3963d09 (diff) | |
| download | chromium_src-5748a5989bf673d62d99fd399e39f263f7982bea.zip chromium_src-5748a5989bf673d62d99fd399e39f263f7982bea.tar.gz chromium_src-5748a5989bf673d62d99fd399e39f263f7982bea.tar.bz2 | |
Docserver: Modify doc inlining so all relevant data is present in availability_finder.py
Not inlining schema nodes for availability finder causes data to go missing and
availability to not be found. Inlining schema nodes means that availability data
gets messed up when a node is no longer inlined, because inlined nodes are
deleted from the schema. Solution: Inline nodes, but do not remove them from the
schema when used in availability_finder.py. This provides all the necessary data,
and doesn't interfere with availability data generation when a node is no longer
inlined because it will be still be present in the schema graphs.
BUG=233982
NOTRY=True
Review URL: https://codereview.chromium.org/385703005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283579 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'extensions/test')
0 files changed, 0 insertions, 0 deletions