The collapse animation in the inline SVG embed was broken on Windows due to
three compounding issues: CSS height transitions don't animate from auto→px in
Electron; the guard direction was inverted for SVGs shorter than canvasHeight;
and the canvas auto-widens when the modal is opened on wide screens
(expandWorld=true), making the real SVG naturalWidth differ from
settings.canvasWidth, causing the computed target height to be larger than the
current rendered height and inverting the animation direction.
Fix: use img.naturalWidth (actual SVG viewBox width) instead of
settings.canvasWidth for the collapsed height calculation. Also moves
touch-action from JS style.setProperty to CSS (.hwm_canvas) to resolve the
Obsidian Required ESLint violation.
Required fixes:
- recognizer.ts: fetch() → requestUrl() (Obsidian API)
- settings.ts: createEl('h2') → Setting.setHeading()
- parser.test.ts: console.log → console.debug (4 occurrences)
- md-parser.ts: remove unnecessary escape in char class [^\s\-] → [^\s-]
- main.ts: async callbacks → void (async()=>{})() pattern; menu as any → as unknown as
- embed.ts / editor-view.ts: innerHTML → setIcon(); key: string → I18nKey; async handlers wrapped in void
- editor-view.ts: setState(state: any) → (state: unknown, result: ViewStateResult); querySelector generic
- i18n.ts: window as any → typed cast; export type I18nKey
- styles.css: CSS utility classes and CSS vars replace inline styles
Bug fixes found during testing:
- setCssProps is a method (el.setCssProps), not a standalone export — caused white modal
- collapse animation broken after expand: replaced rAF with forced reflow (void wrapper.offsetHeight)
- md-parser: // LIST with space not recognized — added \s* after // in both regexes
il posto migliore è il repository Chromium, che è il motore WebView di Android:
- Bug tracker Chromium: https://bugs.chromium.org — cerca "StylusWritingManager" o "stylus handwriting WebView" - Issue del plugin Ink (stessa identica situazione): https://github.com/daledesilva/obsidian_ink/issues/156 — se qualcuno trova un fix lì, vale anche per noi
Il problema è a livello di Chromium/Android WebView, quindi un fix arriverebbe tramite un aggiornamento di Chrome/WebView sul dispositivo, non tramite Obsidian.
