Search Issue Tracker
By Design
Votes
0
Found in
5.5.0a1
Issue ID
780291
Regression
No
[VS] Searching in documentation in VS2015 leads to Online docs, but concrete look-up leads to local docs
Searching in documentation in VS2015 leads to Online docs, but concrete look-up leads to local docs
To repro:
0. VS2015 is set as default editor.
1. Open attached project and open ColorizeBell script.
2. Select, e.g. SpriteRenderer.
3. Press Help -> Unity API Reference.
4. Note: UnityFolder/Editor\Data\Documentation\en\ScriptReference\SpriteRenderer.html is opened in VS2015.
5. Return to script and select List.
6. Press Help -> Unity API Reference.
7. Note: http://docs.unity3d.com/ScriptReference/30_search.html?q=List is opened in VS2015.
Actual result: Behaviour is inconsistent within the product -> similar operations give different results.
Expected results:
If offline docs are installed - VS2015 should open them in any case.
If offline docs are not installed - VS2015 should open online docs in any case.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
Add comment