luminous | block code execution and event collection | Browser Plugin library

This may help you php password_verify not working with database

Check whether the hash is getting stored in database properly or not. Dump the hash you are getting from database and hashed password and check are they same or not.

When loading a JS module you need to explicitly use a relative path. Eg ./chart.js

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules

[EDIT] In addition, you need to run off a server (either locally or remotely). Again, see the MDN module link above.

You need to pay attention to local testing — if you try to load the HTML file locally (i.e. with a file:// URL), you'll run into CORS errors due to JavaScript module security requirements. You need to do your testing through a server.

Here's what I think is happening:

1. Component renders
2. Start fetching definition for "luminous".
3. The definition of "luminous" has finished being fetched. It calls setApiData(data).
4. Component rerenders
5. If you click "luminous", the popper is shown immediately, this is because the data for the popper is ready to use and setSelectedWord("luminous") does nothing.
6. If you click another word, such as "pity", the popper attempts to show, but setSelectedWord("pity") causes the component to start rerendering.
7. Component rerenders
8. Start fetching definition for "pity".
9. The definition of "pity" has finished being fetched. It calls setApiData(data).
10. Component rerenders
11. If you click "pity", the popper is shown immediately, this is because the data for the popper is ready to use and setSelectedWord("pity") does nothing.

Selecting another word will repeat this process over and over.

To fix this, you need to first make use of the show property to show the popover after rendering it out if it matches the selected word. But what if the word appears multiple times? If you did this for the word "her", it would show the popover in multiple places. So instead of comparing against each word, you'd have to assign each word a unique ID and compare against that.

To assign words an ID that won't change between renders, we need to assign them IDs at the top of your component and store them in an array. To make this "simpler", we can abstract that logic into a re-useable function outside of your component:

The problem is in the models you defined. Base on the JSON your models will be:

Konnichiwa @wadakatu, Fred from @imgix here (maintainer of Luminous).

You should be able to make all of your solutions work.

For 1/ I think you need to be able to target only the image that exists within that component, so something like this could work:

I think you should be okay using the :has query: https://developer.mozilla.org/en-US/docs/Web/CSS/:has#Examples

I'll answer about the Deviice not found. The other issues are about local paths.

You can see your package as such (In the next comment, "Package" can be understood as library, but also as an executable, for tests purpose often in the case of "sub packages", or "real executables".

Based on the project documentation, it looks like you can pass a function to the caption.config option:

Captions can be a literal string, or a function that receives the Luminous instance's trigger element as an argument and returns a string.

So you can replace:

There are many things wrong with your code

1. You declare nameOneCompleted inside your if so it's undefined elsewhere. Same for nameTwoCompleted. You should define them in the upper scope
2. Your if condition is always truthy thus useless
3. Use const and let instead of the deprecated var
4. You don't need to do 10 ifs, just define an array and pick the n-th element
5. Use camel case when naming js variables: its nameDecode2, not NameDecode2
6. nameDecode2 was a string of several characters, you probably meant to only take the first one, you don't need to slice nameDecode1 for that btw, just use string index. Also convert it to a number before indexing the string.
7. Don't slice when building substrings, just use substring, it's much easier
8. I don't know what you tried to do with the ellipsis but it was wrong, also be aware that the CSS text-overflow: ellipsis might come more handy than trimming the string on the JS side

That should be good: