-
Notifications
You must be signed in to change notification settings - Fork 32k
JSDoc Intellisense continues to completely remove HTML tag contents #146521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just as an aside, maybe y'all could make the auto-lock-bot a little less aggressive, so that when you make a change that's supposed to resolve an issue, the issue doesn't get locked before the change makes its way into a production release where the reporter can actually confirm that the fix worked. |
Yes that PR only enables the ability for an extension to turn on html rendering. We didn't actually enable it for JS/TS Marking as a feature request to gauge interest |
As I said in my previous issue, I am not making a feature request. I don't need the tag to render as HTML, I need the bare text content to render at all and not be completely discarded. Not showing 80% of the docs for this class is a bug, period. It's frustrating that for years I have had to go look up docs in a browser because my IDE cannot render them without losing random snippets of text. |
The current behavior is by-design. Changing the design is a feature request |
@mjbvz I think my previous comment came off as rude, but I just want to confirm that the official position of the VSCode team is that the following behavior is "by design": Maybe I could re-file this as a security issue? "Attacker can craft documentation with different meanings in different IDEs"? Somebody a little more clever than I could probably come up with something akin to a homograph attack. |
Yes it's by design and it's also not a security issues IMO since this is non-executing code. This is been how VS Code has rendered JSDoc for 5+ years so let's wait for more feedback on the request |
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Issue Type: Bug
The issue I reported a year and a half ago has not been resolved as of the current Insider build of VSCode. The contents of HTML tags in JSDoc comments are still completely removed.
Notice the
<p>
tags containing a large amount of information about this class:That information is not shown in the tooltip and there is no indication that anything has been removed:
Related issues:
#31161
#40607 (marked as resolved via #132182)
#113959
microsoft/language-server-protocol#1344 (LSP says it's not their fault)
cc @mjbvz , who worked the linked PR
VS Code version: Code - Insiders 1.67.0-insider (8b7086a, 2022-04-01T05:16:02.350Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (1)
A/B Experiments
The text was updated successfully, but these errors were encountered: