- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Mar 2020 08:42:46 +0000
- To: public-web-nfc@w3.org
> ignoreRead was added because if you want to write to a tag, that tag might have existing content, and you don't want a read event dispatches for that during the write (as data is already read when the nfc tag is powered up) > What you are saying is that what you just wrote (not previous content) gets dispatched right after it was written? If `ignoreRead` controls the first case (suppress reading of existing content _before_ writing), what should control suppressing reading _after_ writing? 1. `ignoreRead` controls both 2. `ignoreRead` controls the first (as now) and by default we suppress reads right after writes (impl needs to catch and ignore the read intent) 3. we introduce another control option for the second 4. we don't do anything, meaning we'll let the read-after-write dispatched through the system. Opinions? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/551#issuecomment-603106119 using your GitHub account
Received on Tuesday, 24 March 2020 08:42:48 UTC