Skip to content

Commit 7c6f19c

Browse files
committed
Merge branch 'main' into additional-tc53-feedback
2 parents 967fe52 + a7d7c94 commit 7c6f19c

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

.github/workflows/lintyMcLintface.yml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,6 @@ on:
66
workflow_dispatch:
77

88
jobs:
9-
109
bikeshed:
1110
runs-on: ubuntu-latest
1211

@@ -17,14 +16,16 @@ jobs:
1716
- name: setup python
1817
uses: actions/setup-python@v5
1918
with:
20-
python-version: '3.x'
19+
python-version: "3.x"
2120

2221
- name: install bikeshed
2322
run: |
23+
sudo apt-get update
24+
sudo apt-get install libxml++2.6-dev libxslt1-dev
2425
python -m pip install --upgrade pip
2526
pip install bikeshed
2627
bikeshed update
2728
2829
- name: lint
2930
run: |
30-
bikeshed spec index.bs /dev/null
31+
bikeshed spec index.bs /dev/null

index.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,9 +61,9 @@ Conformance {#conformance}
6161

6262
A conforming implementation of this Standard shall provide the interfaces and properties listed in this specification, according to their definition in the corresponding W3C or WHATWG standard. A conforming implementation shall also conform to ECMA-262.
6363

64-
Runtime-specific extensions to any Web Platform API may be implemented by conforming runtimes. Such extensions shall be defined so that their use neither contradicts, nor causes the non-conformance of, normative functionality of any Web Platform API. It is important to carefully consider use of such extensions, as it reduces interoperability and portability of code across runtimes.
64+
Runtime-specific extensions to any Web Platform API may be implemented by conforming runtimes. Such extensions shall be defined so that their use neither contradicts, nor causes the non-conformance of, normative functionality of any Web Platform API. Extending API surface, even without modifying existing API behaviours, should be avoided as it can reduce interoperability and portability of code across runtimes.
6565

66-
This Standard does not prohibit implementing additional Web Platform APIs beyond those listed here.
66+
Runtimes may implement Web Platform APIs beyond those listed in this Standard.
6767

6868
Note: For example, the {{Performance}} API could be extended with additional methods or properties beyond those defined in the [[HR-TIME]] specifications, such as those defined in the [[PERFORMANCE-TIMELINE]] or [[USER-TIMING]] specifications.
6969

0 commit comments

Comments
 (0)