Joshua Horton eae55e4fa1 fix(web): remove extra px offset from last OSK row ... Fixes: #13620 Turns out there was actually a final-row pixel offset being applied for the OSK. I _believe_ this was something originally done for touch-oriented OSKs that ended up applied to all during 17.0's OSK refactoring efforts. kmwosk.css does define layer-group padding above and below (1 px each) for touch keyboards already. Furthermore, things look fine when removing this extra 1px offset on the bottom from the last row. I think we're fine to just drop this minor offset and move on for now.		2025-03-31 10:41:50 +07:00
..
app	Merge pull request #13331 from keymanapp/fix/web/init-should-not-cookie-default	2025-02-26 09:29:54 +07:00
engine	fix(web): remove extra px offset from last OSK row	2025-03-31 10:41:50 +07:00
resources	chore(web): try lighter color	2024-03-10 15:36:00 -05:00
samples	chore(common): builder scripts now use /resources/build/builder.inc.sh	2024-05-02 15:54:31 +07:00
test	Merge pull request #13331 from keymanapp/fix/web/init-should-not-cookie-default	2025-02-26 09:29:54 +07:00
tools	refactor(web): merge device-detect with web/src/engine/main	2024-09-11 16:48:15 +02:00
.editorconfig	change(web): source/ => src/	2022-10-21 12:00:10 +07:00
tsconfig.all.json	chore(web): centralizes main KMW component tsconfig settings	2023-06-14 09:02:46 +07:00
tsconfig.dom.json	chore(web): the final push for config-flag parity for web/	2024-05-29 10:57:41 +07:00