This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following FunctX tests only work when the static timezone is +02:00 (although the results on the FunctX website are given for an implicit timezone of -05:00) functx-fn-adjust-dateTime-to-timezone-6 functx-fn-adjust-dateTime-to-timezone-7 functx-fn-adjust-dateTime-to-timezone-all functx-fn-adjust-date-to-timezone-5 functx-fn-adjust-date-to-timezone-6 functx-fn-adjust-date-to-timezone-all functx-fn-adjust-time-to-timezone-5 functx-fn-adjust-time-to-timezone-6 functx-fn-adjust-time-to-timezone-7 functx-fn-adjust-time-to-timezone-8 functx-fn-adjust-time-to-timezone-all functx-fn-implicit-timezone-1 I can think of 4 possible solutions: 1) Rewrite the adjust tests to compare the timezone with implicit-timezone(), and drop the implicit-timezone-1 test; although this will be quite messy in some cases and loose the succinctness of the tests. 2) Specify that the entire test suite should be run in a particular timezone (eg. +02:00). 3) Add another element/attribute/role to the test-cases to specify the timezone in which a test must be run. This is my preferred solution. 4) Remove these tests entirely.
We ran into this issue long ago. My recollection is that agreed to use explicit timezones in most of our test cases, and to use Z as the expected value of the implicit timezone in just a small number of the test cases. Perhaps I recall wrongly, or perhaps we changed this over time. I went looking for precedent, and found that in fn-implicit-timezone-2 that we expect "-PT5H" and the comparator is Inspect.
Anyhow, it needs fixing. I didn't have the measures for reviewing each test individually -- things like this will crop, but I believe it will be relatively few issues.
I've tried to fix this in CVS. These files are generated and it's not the easiest thing to get an overview of so it's very likely I've missed something here.
These tests have all been removed/fixed correctly, with the exception of the expected result for functx-fn-adjust-time-to-timezone-all.
Yeah, updated version in CVS, I hope it's right.