Web This site Trusted
19 result(s) for “if com target site whattodrink com site spec openapi org site:www.w3.org” of 49 matched · page 2 · 686 ms
Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.
Did you mean if com target site whattodrink com site spec openai org site:www.w3.org?
Freshness: newest result fetched 23 d ago · median age of these results 23 d · 14 of 19 carry a fetch time
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29709
I suppose the example has not been (completely) corrected since earlier versions of the spec where merge groups and keys were accessible as variables
https://www.w3.org/2003/12/22-dom-core-issues/issues.html
From my reading of the spec [1], what should happen is that first the child node should be removed ("If the newChild is already in the tree, it is first removed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29445
If you would agree, I'll update the expected result
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29449
Intuitively, if we know that the "base expression" (the function) is a map or an array, and the argument is motionless, then the dynamic function call itself is motionless; if we don't know (because the type analysis doesn't tell us), then we can't determine that the expression is guaranteed-streamable, and the user
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29460
org/Archives/Public/public-xsl-wg/2016Jan/0002
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30002
org/TR/xslt-30/#memoization respectively listed in https://www
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29340
1, but we require its support even if you don't support the XPath 3
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29752
org/1999/XSL/Transform"
xmlns:xs="http://www
https://www.w3.org/blog/2020/listen-to-the-people-the-future-of-epub-and-new-directions-for-publishing-w3c/
If you haven’t yet taken the survey, go to the survey and let us know what you think
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29234
A mode is declared if the package contains an xsl:mode declaration for that mode, or if the mode is a public or final mode accepted from a used package
https://www.w3.org/2019/03/07-webauthn-minutes.html
RP wants passwordless, resident key, if they can
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29880
I wasn't aware of the 16 digit limitation, I don't see that in the spec
https://www.w3.org/wiki/Main_Page
Work being done to improve specs in general:
SpecProd - an effort to restyle spec content design
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29442
- make explicit, or add a note, that if Complex/Simple is not in effect, normalization does NOT take place and text nodes, even empty ones, are not concatenated, nor removed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29697
* This sequence will be merged with the sequences defined by other xsl:merge-source elements, if present
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29692
5:
If xsl:strip-space or xsl:preserve-space declarations appear within a library package, they only affect calls to the docFO30 or document functions appearing within that package
https://www.w3.org/International/i18n-drafts/nav/about
If you do, you will build applications and content that, in fact, present barriers for the use of your technology or content by many people around the world
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29738
29738 – [XSLT30] (editorial) We shouldn't use the term "streamable stylesheet" in the spec
Bugzilla – Bug 29738 [XSLT30] (editorial) We shouldn't use the term "streamable stylesheet" in the spec Last modified: 2016-10-06 18:42:25 UTC
This is an archived snapshot of W3C's public bugzilla bug tracker
https://www.w3.org/blog/2019/publishing-wg-telco-2019-10-21-closing-some-open-issues/
: the group agreed that the presence of these terms are RECOMMENDED (although not required
Bounds of an audiobook: the concept of "bounds" are present in the audiobook spec (normatively) and in the publication manifest spec (non-normatively)