Grammalecte  Check-in [d353472e17]

Overview
Comment:[doc] Web API update
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk | doc
Files: files | file ages | folders
SHA3-256: d353472e17fad87a2c15424eb98f0db91bf82a1986dbfeaa0b58a39f0fcd5cfb
User & Date: olr on 2020-03-19 08:20:31
Other Links: manifest | tags
Context
2020-03-19
08:25
[doc] Web API update check-in: 0bdd05e68d user: olr tags: doc, trunk
08:20
[doc] Web API update check-in: d353472e17 user: olr tags: doc, trunk
08:19
[doc] Web API update check-in: 6727222f1a user: olr tags: doc, trunk
Changes

Modified doc/API_web.md from [c344f75300] to [041f12ee10].

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

### How it works

Usually, webpage scripts can’t call methods or functions of browser extensions.

The Grammalecte API is injected within your webpage, with methods launching events that Grammalecte is listening. When Grammalecte receives one of these events, it launches the requested tasks. Results may be sent via events on webpage nodes.

For information purpose only, here are the layers of code explaining with you can’t access directly to the grammar checker:

    ·> webpage script
    <> Grammalecte API (injected by the content-script, callable by the webpage script)
    <> Content-script (injected by the extension, not callable by the webpage script)
    <> Background script (extension core)
    <· Worker running the grammar checker on a different process








|







23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

### How it works

Usually, webpage scripts can’t call methods or functions of browser extensions.

The Grammalecte API is injected within your webpage, with methods launching events that Grammalecte is listening. When Grammalecte receives one of these events, it launches the requested tasks. Results may be sent via events on webpage nodes.

For information purpose only, here are the layers of code explaining why you can’t access directly to the grammar checker:

    ·> webpage script
    <> Grammalecte API (injected by the content-script, callable by the webpage script)
    <> Content-script (injected by the extension, not callable by the webpage script)
    <> Background script (extension core)
    <· Worker running the grammar checker on a different process