Giter VIP home page Giter VIP logo

josias-r / boarding.js Goto Github PK

View Code? Open in Web Editor NEW
103.0 2.0 3.0 2.16 MB

A light-weight, no-dependency, vanilla JavaScript engine to create powerful onboardings and drive the user's focus across the page

Home Page: https://josias-r.github.io/boarding.js/

License: MIT License

HTML 22.33% CSS 7.70% TypeScript 69.75% JavaScript 0.21%
spotlight popover overlay tour feature-introductions focus-shifters overlays user-onboarding walkthrough javascript

boarding.js's Issues

Edit the svg to change the values of the highlighted element

Good morning, how could you edit the lighting of the svg strokes or when you do, do not re-edit and return to its original values if I scroll or remove the scroll. I am calculating some width and height values once the element has been illuminated to edit it, then I create again the string of the svg path’s d attribute to change it with jquery but then if the scroll changes or if the illuminated element is a select, if I select one of your options it also returns to its original values.

Enhancement: Support for IDs starting with numbers or consisting of only numbers

Some of the IDs I use start with numbers, and it is common to use IDs that are generated at runtime with numbers or alphanumeric characters. For some unknown reason, querySelector doesn't support this structure. I am attaching an image of the error generated using the compiled version from the master branch on May 17, 2023.

image

Help Wanted🙏🏻: External monitor causes an offset of the highlighted element and the cutout

more details

Screenshot 2023-01-12 at 08 29 11

Findings so far (macos):

  • It does not happen without external monitor
  • It happens when an external 16:9 monitor is connected
    • It also happens when two 16:9 monitors are connected
  • It happens when monitors "extend" screen but also when they "mirror" the built-in screen
  • It does not happen with a external wide-screen monitor connected
  • It is NOT about screen size. It also happens on the laptop's original screen, if the above conditons apply

Feature✨: Support promise step-handling out of the box

The preventMove + continue API can already be used to easily write async step-handling.

This could be simplified by supporting promises out of the box.

So this:

onNext: async () => {
   boarding.preventMove();
   await myPromise();
   boarding.continue();
},

Could become this:

onNext: async () => {
   await myPromise();
},

Where continue & preventMove are auto handled by the library in the background in case a promise is returned from the handler.

The automated release is failing 🚨

🚨 The automated release from the next branch failed. 🚨

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

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 fix 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 next branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.


The release 3.3.5 on branch next cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=3.4.0 can be published from branch next.

The following commit is responsible for the invalid release:

  • fix: add keywords to npm package (649bdb7)

This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch next with git revert or git reset.

A valid branch could be master or next.

See the workflow configuration documentation for more details.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Cannot use CDN

Hello, I am trying to include this library as a CDN on my website, but I get error: Uncaught SyntaxError: export declarations may only appear at top level of a module

Problem is with this line, which is at the end of the file:

export {
  it as Boarding
};

CDN: view-source:https://unpkg.com/[email protected]/dist/main.js

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.