Repository navigation
docs: plain-language parity page and stale-claim fixes - #29
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrites the Electron parity page (
/docs/migrating/parity) so a developer can read it without knowing Bunmaska's internals.What changed
Map,Set,ArrayBufferand typed arrays (checked by running the encoder); it does not turn them into plain objects.ipc-main.mdandwebContents.sendsaid the same wrong thing and are fixed too.safeStorageshares one key on Windows as well as macOS and Linux.webContentsandpowerMonitorare partial, not full.sendInputEventon Windows now carries mouse buttons and scan codes; the page andweb-contents.mdsaid it didn't.BUNMASKA_ENABLE_LINUX_POWER_BLOCKER.screen.tsdoc comment said macOS reports no work area or display origins; it does.moveandresizeevents arrive only when a drag ends.centerandsetAlwaysOnTopdo nothing.shell.openExternalresolvesfalseinstead of rejecting.How it was checked
A writer rewrote the page. Three reviewers then read it: a fact-checker compared every claim with the code and cited file:line, an Electron developer who had never seen the codebase flagged anything unclear, and a style checker covered markup, anchors and dashes. The writer then revised it using their notes.
bun run validatepasses in the repo and inwebsite/.🤖 Generated with Claude Code