Errors such as buffer overruns are non-fatal. After the ReadableStream closes with an error the SerialPort's readable attribute is replaced by a new ReadableStream. Reilly Grant | Software Engineer | [email protected] | Google Chrome <https://www.google.com/chrome>
On Thu, Sep 14, 2023 at 1:07 AM amir karimi <[email protected]> wrote: > Hi, > > I hope you are well. > > I have been trying o get WebSerial working in my React app. It works fine > in ideal conditions. However, if the serial device spams the serial port > with a lot of data very fast before serialport.connect() happens, I get > "BufferOverrunError". > I increased the buffer size from 255 to 4095 but still it fails. Is there > any method to empty the buffer or recover from the error when this happens? > > Thanks, > > Amir > On Tuesday, September 18, 2018 at 5:50:38 PM UTC+1 Reilly Grant wrote: > >> The UI treatment will mirror that of WebUSB. The lack of content settings >> and page info listings for Web Bluetooth permissions is a bug and will be >> fixed when persistent permissions are implemented, as they are for WebUSB. >> Reilly Grant | Software Engineer | [email protected] | Google Chrome >> <https://www.google.com/chrome> >> >> >> On Mon, Sep 17, 2018 at 5:56 PM Lucas Garron <[email protected]> wrote: >> >>> Do you have any specific plans for UI treatment and content settings yet? >>> >>> Bluetooth pairing has special case (tab icon only, no content setting or >>> page info listing) that doesn't scale to many permissions, and I would >>> personally like to see focus on the mental model of Page Info as the >>> one-stop-shop for info and management of the current page's permissions. >>> >>> »Lucas >>> >>> On Mon, Sep 17, 2018 at 4:51 PM Reilly Grant <[email protected]> >>> wrote: >>> >>>> Contact emails >>>> >>>> [email protected] >>>> >>>> Explainer >>>> >>>> https://github.com/reillyeon/serial/blob/explainer/EXPLAINER.md >>>> >>>> Spec >>>> >>>> https://wicg.github.io/serial >>>> >>>> Summary >>>> >>>> The Serial API provides an interface for connecting to physical and >>>> virtual serial ports. It will share the same chooser-based permissions >>>> model as other hardware APIs such as Web Bluetooth and WebUSB. Development >>>> of the specification will proceed in parallel to implementation. >>>> >>>> Motivation >>>> >>>> Operating systems require applications to use different APIs depending >>>> on what interface a device exposes. The Serial API fills a gap left by Web >>>> Bluetooth and WebUSB where devices which implement a serial port interface >>>> are not covered by neither the former (because it does not support >>>> Bluetooth Classic) nor the latter (because a system driver has already >>>> claimed exclusive access to the device). >>>> >>>> Risks >>>> >>>> Interoperability and Compatibility >>>> >>>> The primary risk of this API is that it will not be implemented by >>>> other vendors. It shared a lot with the Web Bluetooth and WebUSB APIs which >>>> so far have only been implemented by Chrome. While there have been no >>>> public signals from Edge and Safari it is clear from the fact that the >>>> original specification was abandoned by Mozilla (and their reaction to >>>> similar specifications) that Firefox’s position is negative. Web >>>> developers, commenting on the proposal to incubate this specification in >>>> the WICG, have displayed overwhelmingly positive support because of the >>>> possibilities it opens up for supporting additional hardware devices. >>>> >>>> Edge: No signals >>>> >>>> Firefox: Negative signals >>>> >>>> Safari: No signals >>>> >>>> Web developers: Positive signals >>>> <https://discourse.wicg.io/t/serial-api-moving-from-web-of-sensors-cg-to-web-incubator-cg/2940> >>>> >>>> Ergonomics >>>> >>>> Developers using this API may also be building applications that use >>>> other hardware APIs such as Web Bluetooth and WebUSB. Each of these >>>> interfaces have differences that reflect the underlying transport however >>>> we should be sure that user-facing abstractions such as permissions are >>>> handled in a consistent way. Integration with the Permissions API could, >>>> for example, permit authors to request permission to access a device across >>>> multiple API surfaces, this solving the problem of a device which may be >>>> accessible via the Serial API on platforms which include a driver for it, >>>> with a fallback to WebUSB on platforms without. >>>> >>>> Activation >>>> >>>> Developers should be able to take advantage of this API immediately. >>>> Those using the chrome.serial API (only available to Chrome Apps) will find >>>> it relatively easy to port their applications. >>>> >>>> Debuggability >>>> >>>> This is a JavaScript interface supported by the existing DevTools >>>> debugger. >>>> >>>> Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, Chrome OS, Android, and Android WebView)? >>>> >>>> This feature will be supported by all platforms except Android WebView. >>>> >>>> Is this feature fully tested by web-platform-tests >>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >>>> ? >>>> >>>> No, but it will be. >>>> >>>> Link to entry on the feature dashboard <https://www.chromestatus.com/> >>>> >>>> https://www.chromestatus.com/feature/6577673212002304 >>>> >>>> Requesting approval to ship? >>>> >>>> No. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "blink-dev" group. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEmk%3DMZAA3cQqnjYvZQzs4L1xWF3%3DbM0aruAsiJW74o%2BqGc_DQ%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEmk%3DMZAA3cQqnjYvZQzs4L1xWF3%3DbM0aruAsiJW74o%2BqGc_DQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> >> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANCvrdRFGkAsQ2%3DitED8j0Gt7ut7BYoWwni9xy6PoNQ5NgwRmg%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANCvrdRFGkAsQ2%3DitED8j0Gt7ut7BYoWwni9xy6PoNQ5NgwRmg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEmk%3DMbYsencAoj4qyzgjgCLMSR36rUJRz79n48g0gad4Qc2pw%40mail.gmail.com.
