Modern IDB: DatabaseProcess cannot open some database filenames that DumpRenderTree can This is forcing us to skip these two tests when enabling Modern IDB in WK2: storage/indexeddb/database-odd-names.html storage/indexeddb/odd-strings.html Just one example that both tests hit is the database name with two unicode bytes "0xfffe" The database filename that resolves to on my machine is: /Volumes/Data/Home/Library/Application Support/DumpRenderTree/Databases/IndexedDB/file__0/<funny question mark in a box glyph>/IndexedDB.sqlite3 DRT opens it fine, but DatabaseProcess does not. Currently unclear to me what's going on, but with the right eyes on it I'm sure it will be obvious.
*** Bug 154975 has been marked as a duplicate of this bug. ***
New title: Modern IDB: Tests fail due to odd strings in names