postcompose event "0x80004005 (NS_ERROR_FAILURE)" error
See original GitHub issueHi there, i am stuck with 0x80004005 (NS_ERROR_FAILURE)
error on postcompose event.
Its strange, because in demo project it works fine, native ol in vue does not generate any problems too.
full error message:
[Vue warn]: Error in event handler for "postcompose": "[Exception... "Failure" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: webpack-internal:///./node_modules/ol/style/RegularShape.js :: draw_ :: line 444" data: no]"
edit: in project i was using vue-cli with default build settings.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
0x80004005 (NS ERROR FAILURE) and other firefox errors
To figure out what failed, look for the origination function. For example, in: [Exception... "Component returned failure code: 0x80004005 ( ...
Read more >what does this error mean Request unsuccessful: nsresult ...
This is an old post but thought worth to mention, I got this error when destination page was on same domain but on...
Read more >Component returned failure code: 0x80004005 ...
Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWindowsRegKey.open]. How to resolve this error please.
Read more >Component returned failure code: 0x80004005 ...
While looking at issue 69, I get a very similar but slightly different error message. I am running bluegriffon 3.1.2 on Ubuntu Linux...
Read more >You may receive error code 0x80004005 or other ...
When you try to start a Microsoft Windows XP-based computer, you may receive an error message that contains different error codes. This article...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Now I got it.
You are using cluster source, so really on the map only clustered features are rendered, not your original feature. And this is why programmatic addition of origin feature to select collection don’t replace the default vector source style, cause actually this is another feature. When you click by the feature, the clustered feature appending to select interaction overlay, and this hides it from vector source.
So to programmatic select the clustered feature by the original feature, you should find the current cluster in which original feature added.
Take a look at the update example https://jsfiddle.net/ghettovoice/bo8fm4j2/ First of all I switch vuelayers to latest stable
v0.11.9
inside resources. Then I add synchronization of clustered features to the data property. And finally lookup the cluster by the included original feature.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.