Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by remram on Friday June 30, 2023 @09:59PM
(#36545531)
When the form submits its frame refreshes ("navigates").
Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by ComputerGuru on Friday June 30, 2023 @10:10PM
(#36545625)
Right but reloading a static html asset (the reply iframe consisting of just a textbox) is basically free. So long as you separate the chat history window and the reply textbox/form into two separate frames, I don’t see the problem.
Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by croshan on Friday June 30, 2023 @11:39PM
(#36546235)
Using JavaScript is also “basically free”.
There’s no problem with either listed approach, GP just seems to consider a method without page reloads as adhering to a harder constraint.
Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by weird-eye-issue on Saturday July 01, 2023 @06:06AM
(#36548499)
Using JS would have broken the threat model of the dark web chatroom. So it is a non starter in that context.
Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by bawolff on Saturday July 01, 2023 @07:01AM
(#36548796)
I thought chrome killed x-mixed-replace (except for jpg images)
Re:GitHub – kkuchta/CSS-only-chat: A monstrous async web cha...
by ComputerGuru on Sunday July 02, 2023 @01:36PM
(#36563620)
Mentioned above: https://news.ycombinator.com/item?id=36545326
Edit: actually this should work even without mixed replace.