News for hackers. Stuff that matters.
Re:TerarkDB, ByteDance's RocksDB replacement by josephg on Wednesday December 23, 2020 @03:40AM (#25515686)
Your all-in-one docs[1] refuse to render at all in firefox? Seems like a strange restriction, and disappointing that it doesn't even let you read the document in non-webkit browsers. Feels like the IE days all over again.

"An error occurred. This browser is not supported, click here to learn more."

[1] https://bytedance.feishu.cn/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Re:TerarkDB, ByteDance's RocksDB replacement by ddorian43 on Wednesday December 23, 2020 @06:02AM (#25516420)
It renders on ubuntu 18.04 Firefox but also displays "This browser not supported with https://www.feishu.cn/hc/en-us/articles/360038713913". Probably doesn't support linux.
Re:TerarkDB, ByteDance's RocksDB replacement by royguo1988 on Thursday December 24, 2020 @12:34AM (#25525294)
This is wired, I will call our internal Lark team to deal with it.
Re:TerarkDB, ByteDance's RocksDB replacement by erk__ on Wednesday December 23, 2020 @09:37AM (#25517974)
I get the same on Windows 10 so it is probably the browser.
Re:TerarkDB, ByteDance's RocksDB replacement by oefrha on Wednesday December 23, 2020 @04:40AM (#25516017)
Works perfectly for me in Firefox (macOS). Might be a misleadingly worded "something went wrong, we don't know what" message. Probably want to check your console, could be a network problem.
Re:TerarkDB, ByteDance's RocksDB replacement by josephg on Wednesday December 23, 2020 @04:34PM (#25522484)
Yeah there's some unreadable minified error stack traces in the console. Weirdly it seems to load fine and I can scroll the content for a second or two while its still loading in. Then it puts up an error dialog and I can't access the content any more. Once thats happened if I reload the page the error dialog comes up immediately and the page doesn't bother loading behind it.

I'm on firefox on MacOS too, and it happens with my ad blocker on or off. Chrome works fine. The support document linked in the error explicitly says only chrome and safari are supported on macos. I'm confused why my grandparent comment has been downvoted - this is a real bug report stopping me (and maybe others) from reading documentation that looks to have a lot of thought put into it. And given the content seemed to be loading fine before the error message came up, well, it feels forced.