|
|
|
@ -78,7 +78,7 @@ and then files in `src/frontend` and `src/shared` are served at `/frontend` and |
|
|
|
|
|
|
|
|
|
|
|
### User interface / handling interactions |
|
|
|
### User interface / handling interactions |
|
|
|
|
|
|
|
|
|
|
|
Of course the obvious choice would be to implement everything in React or another reactive framework, |
|
|
|
Of course the obvious choice would be to implement everything in React or another similar framework, |
|
|
|
but where is the fun in that? |
|
|
|
but where is the fun in that? |
|
|
|
I wanted to minimise the size of the resulting frontend application, |
|
|
|
I wanted to minimise the size of the resulting frontend application, |
|
|
|
and the best way to reduce the number of dependencies on frontend is to not have any dependencies, |
|
|
|
and the best way to reduce the number of dependencies on frontend is to not have any dependencies, |
|
|
|
@ -301,7 +301,7 @@ None. |
|
|
|
https://github.com/WebKit/standards-positions/issues/97. |
|
|
|
https://github.com/WebKit/standards-positions/issues/97. |
|
|
|
Everything should still work in online mode, falling back on client-server communication. |
|
|
|
Everything should still work in online mode, falling back on client-server communication. |
|
|
|
* Servo: checked, does **not** work in nightly as of 2024-11-20, and I don't have an opportunity to figure out why |
|
|
|
* Servo: checked, does **not** work in nightly as of 2024-11-20, and I don't have an opportunity to figure out why |
|
|
|
(it's not packaged for Alpine, their regular Linux builds don't work on Alpine, |
|
|
|
(it's not packaged for Alpine (...yet), their regular Linux builds don't work on Alpine, |
|
|
|
so I had to check it on someone else's Windows machine). |
|
|
|
so I had to check it on someone else's Windows machine). |
|
|
|
|
|
|
|
|
|
|
|
## Known issues and quirks |
|
|
|
## Known issues and quirks |
|
|
|
|
