4 ms·
I mentioned multipart/x-mixed-replace above and I think it can work here instead of CSS. You never reload the chat history page, just put that in an iframe and
by ComputerGuru 3y ago
I mentioned multipart/x-mixed-replace above and I think it can work here instead of CSS. You never reload the chat history page, just put that in an iframe and use a separate iframe with a form that submits your newest reply.
Edit: actually this should work even without mixed replace.
- remram 3y agoWhen the form submits its frame refreshes ("navigates").
- ComputerGuru 3y agoRight 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.
- croshan 3y agoUsing 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.
- weird-eye-issue 3y agoUsing JS would have broken the threat model of the dark web chatroom. So it is a non starter in that context.
- bawolff 3y agoI thought chrome killed x-mixed-replace (except for jpg images)
- ComputerGuru 3y agoMentioned above: https://news.ycombinator.com/item?id=36545326 https://news.ycombinator.com/item?id=36545326