|
|
Rank: Newbie
Groups: Member
Joined: 12/7/2017
Posts: 9
|
We have a (WPF) application that makes use of the web IndexDB
This used to work for EO.WebControls based on Chromium <= 81 (EO2017-2020)
Sample Code
window.indexedDB.open(`MyId`, 1);
This throws the exception on EO 21.0.32
"Internal error opening backing store for indexedDB.open (DOMException)
We have set the cache folder for the user to %TEMP% so the preveliges should be sufficient.
Regular Chrom 86 is able to load IndexDB.
The IndexFolder on the cache folder is created but noting more...
Is there an additional security or do we have actively to enable IndexDB
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
We tested the code here and it appears to work fine. Our steps are as follow:
1. Run TabbedBrowser sample application;
2. Load Google's home page;
3. Click menu -> Console to display the console pane;
4. Type "window.indexedDB.open(`MyId`, 1)" enter;
We did not get any error. Can you try it on your end and see if it works for you?
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/7/2017
Posts: 9
|
window.indexedDB.open(`MyDB`, 1) in EOBrowser does not throw an exception this is actually correct, but it is not created neither
If I do the same in chrome then the db gets created.
The problem is when you try to access then the db
I went back to 21.0.18 and there it also does not work
Went back to 20.3.34 and then everything is fine.
(20.3.63) does not work as for the defect "EO worker process (eowp.exe) can not be used by more than one process"
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi, In that case you can try to isolate the problem into a test project: https://www.essentialobjects.com/forum/test_project.aspxWe won't be able to conclude that something is not working just because you don't see a specific file somewhere as these kind of implementation details can change from time to time. However if you can provide a test project for us to demonstrate the problem we will be able to investigate further. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/7/2017
Posts: 9
|
H after reading in the support forum about the java script exception and local storage fixes in 21.0.62 I decided to give it a try.
It is fixed. The indexDB is now properly written to the defined cache folder.
Reverted back to 21.0.32 and the error is there again, back to build 62 and it works.
Seems there must be a side effect
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Great. Thanks for the update!
|
|