Code Monkey home page Code Monkey logo

vscode-html-preview's Introduction

travis build Version Renovate enabled

Html Preview for VSCode

demo

Commands

Command Keybinding
Html Preview: Open ctrl+alt+p
Html Preview: Close Preview Server none

Credits

Much of this project is based on the Live Preview feature by Brackets

vscode-html-preview's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

vscode-html-preview's Issues

No live update when base tag used

Using the HTML below somehow breaks the live update. If you remove the base tag and re-open the preview window, it will work again.

<!DOCTYPE html>
<html>
  <head>
    <base href=http://www.example.com/ target=_self />
  </head>
  <body>
    asdasdasdasdasdasd
  </body>
</html>

However, that is not the only thing, as this HTML doesn't get fixed when I remove the base tag, so there has to be other tags breaking the extension.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No "name" found in package.json.

Unfortunatly this error doesn't have any additionnal information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful informations.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Prompt-blocking behavior from the perviewer

Goodday,

I found another bug (which might be one for the underlaying js project?)
I setup a small testcase so you can see what the problem is.

Test case:

<!DOCTYPE html>
<html>
<head>
</head>
<body>
    <div>testing</div> <!-- try to type this line in preview mode on browser -->
</body>
</html>

Steps to reproduce:

  1. create a file with an empty html template (like above, excluding the div element).
  2. open the preview (if you open it in browser you'll get the notifications, in VSCode it simply freezes without notifications, as javascript is verry restricted in VSCode).
  3. start typing the element without autocompletion
  4. watch the magic happen.

Error message

errorhighlight error, node 11 doesn't exist

In this case it gave the element the number 11 but it can be any element/number. I get that the html structure is invalid, so that it is not highlighting correctly is fine (since I am still typing). The problem is that it is prompting, and therefore blocking all javascript executions. Since the event queue contineus when you type further, the popup seems to be 'unhidable' as the same error is generated for every single event it runs behind. This not only blocks javascript events, it also blocks the updating of the html-preview itself (hence the blocking in VSCode)

My solution is to simply refresh the browser, after which you only need to click the popup away once. But that is an extra step this plugin should prevent IMO (pressing f5 after every change).
If I have the preview in VSCode, there is no way to refresh the embedded browser, So than I have to close the preview, and reopen it (which is also not ideal).

Proposed solution:

As you mentioned in another issue post, there were problems with the tbody element, I would propose a 2step process for the highlighting and updating?

As you cannot expect the html structure to be perfect (half-typed elements, unclosed elements etc.), I would propose a 'validation-step' before 'reacting' on the event send from VSCode? So when it senses its html structure is invalid, simply abort advanced highlighting stuff and put something in the logs instead of trying to prompt everytime?

Once it has been invalid, and it senses a valid HTML structure again, simply rebuild the structure (as it is doing when you first open the preview) and everything should work fine. This step can also be used to 'fix' the tbody issue I guese?

As a side-note I would advice to add a logging-level setting for the plugin, as one might be more interested in errors from his own javascript rather than a spam of this plugin?

version details:
Html Preview 1.21.5

If you need more information, feel free to ask!

Live preview stop working

Live preview sometimes stops working in certain occasions. The webpage just keep freezing and cannot reload the page.

Some occasions that make this happen are :

  • try to comment and remove comment continuously on any css code for 8 times or more.
  • link and unlink css file.
  • when working on css file the live preview often got bugged and stopped working

My browser : Mozilla Firefox v75.0

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (default:timezone(Europe/Berlin)). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.