mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-30 14:14:09 +02:00
Compare commits
4 commits
7a277efcf1
...
1cef528962
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1cef528962 | ||
|
|
c578129bed | ||
|
|
0a76482118 | ||
|
|
7f35431eb7 |
1
changelogs/client_server/newsfragments/2299.feature
Normal file
1
changelogs/client_server/newsfragments/2299.feature
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
Clients supporting the `ol` HTML element must also support the `start` attribute, as per [MSC4313](https://github.com/matrix-org/matrix-spec-proposals/pull/4313).
|
||||||
|
|
@ -0,0 +1 @@
|
||||||
|
Clarify what the `minimum_valid_until_ts` field means when it is set in key queries.
|
||||||
|
|
@ -84,6 +84,10 @@ Additionally, web clients should ensure that *all* `a` tags get a
|
||||||
`rel="noopener"` to prevent the target page from referencing the
|
`rel="noopener"` to prevent the target page from referencing the
|
||||||
client's tab/window.
|
client's tab/window.
|
||||||
|
|
||||||
|
{{% added-in v="1.18" %}} Clients that support rendering numbered lists via the
|
||||||
|
`ol` tag MUST also support the `start` attribute in order to prevent loss of
|
||||||
|
meaning of a message due to the numbering of list items.
|
||||||
|
|
||||||
Tags must not be nested more than 100 levels deep. Clients should only
|
Tags must not be nested more than 100 levels deep. Clients should only
|
||||||
support the subset of tags they can render, falling back to other
|
support the subset of tags they can render, falling back to other
|
||||||
representations of the tags where possible. For example, a client may
|
representations of the tags where possible. For example, a client may
|
||||||
|
|
|
||||||
|
|
@ -34,10 +34,10 @@ paths:
|
||||||
- in: query
|
- in: query
|
||||||
name: minimum_valid_until_ts
|
name: minimum_valid_until_ts
|
||||||
description: |-
|
description: |-
|
||||||
A millisecond POSIX timestamp in milliseconds indicating when the returned
|
A millisecond POSIX timestamp. The returned keys SHOULD be valid
|
||||||
certificates will need to be valid until to be useful to the requesting server.
|
until at least this timestamp.
|
||||||
|
|
||||||
If not supplied, the current time as determined by the notary server is used.
|
If not supplied, the notary server MUST use the current time.
|
||||||
required: false
|
required: false
|
||||||
example: 1234567890
|
example: 1234567890
|
||||||
schema:
|
schema:
|
||||||
|
|
@ -98,12 +98,11 @@ paths:
|
||||||
type: integer
|
type: integer
|
||||||
format: int64
|
format: int64
|
||||||
description: |-
|
description: |-
|
||||||
A millisecond POSIX timestamp in milliseconds indicating when
|
A millisecond POSIX timestamp. The returned keys
|
||||||
the returned certificates will need to be valid until to be
|
SHOULD be valid until at least this timestamp.
|
||||||
useful to the requesting server.
|
|
||||||
|
|
||||||
If not supplied, the current time as determined by the notary
|
If not supplied, the notary server MUST use the
|
||||||
server is used.
|
current time.
|
||||||
example: 1234567890
|
example: 1234567890
|
||||||
required:
|
required:
|
||||||
- server_keys
|
- server_keys
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue