Skip to content
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.

Sign up for GitHub

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

Jump to bottom

<style> tag breaks VF Language Server #5602

Closed
ChuckJonas opened this issue May 16, 2024 · 1 comment
Closed

<style> tag breaks VF Language Server #5602

ChuckJonas opened this issue May 16, 2024 · 1 comment

Comments

@ChuckJonas
Copy link

ChuckJonas commented May 16, 2024 •
edited
Loading

Summary

Adding a <style> tag to a VF page breaks the VF language Server in vscode.

Steps To Reproduce:

  1. Create a new VF page
  2. Add this content
<apex:page applyHtmlTag="false"  showHeader="false" sidebar="false" standardStylesheets="false">
    <html>
        <head>
            <style> body { font-family: 'Arial Unicode MS'; } </style>
        </head>
    </html>
</apex:page>
  1. Save

Expected result

There should be no issues and the language server should continue to work

Actual result

The end of the style tag gets marked with a red syntax error (but no "problem"). After saving, the following error when be output:

[Error - 2:02:13 PM] Request textDocument/rangeFormatting failed.
  Message: Request textDocument/rangeFormatting failed with message: js_source_text is not defined
  Code: -32603

When this happens, prettier formatting no longer works.

Additional information

QuoteContract_page_—_realself

Salesforce Extension Version in VS Code: v60.13.0

Salesforce CLI Version: @salesforce/cli/2.41.8 darwin-arm64 node-v20.12.

OS and version: OSX

VS Code version: 1.87

Most recent version of the extensions where this was working: No idea
@daphne-sfdc
Copy link
Contributor

Hi @ChuckJonas, We are aware of this issue - it's the same one as #5593 which was also filed this week. We have filed a bug for this in our backlog from the previous issue and will add this occurrence to our bug.

Closing this issue, as it is a duplicate issue.

@daphne-sfdc daphne-sfdc closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChuckJonas @daphne-sfdc