Project

Profile

Help

Bug #2724

Single digit hours in parse-ietf-date()

Added by Debbie Lockett over 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Category:
XPath conformance
Sprint/Milestone:
Start date:
2016-04-22
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.7, trunk
Fix Committed on Branch:
9.7, trunk
Fixed in Maintenance Release:

Description

Following the resolution of W3C bug #2496, changes have been made to the F&O 3.1 specification of parse-ietf-date() to allow single digit hours (in the time or timezone offset). Saxon 9.7 currently disallows these.

History

#1 Updated by Debbie Lockett over 4 years ago

  • Status changed from New to In Progress
  • Applies to branch 9.8 added

Looking at the ParseIetfDate class, I have noticed that currently we do not check that the returned time and timezone values are valid. (Note that there is a check that the date is valid; and the TimeValue constructor used performs no validation). This should also be added.

#2 Updated by Debbie Lockett over 4 years ago

  • Status changed from In Progress to Resolved
  • Fix Committed on Branch 9.7, 9.8 added

ParseIetfDate parseTime method updated to allow single digit hours. Further improvements to add validation for the time value.

Patch committed on 9.7 and 9.8 dev branches.

#3 Updated by O'Neil Delpratt over 4 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.7.0.5 added

Bug fix applied in the Saxon 9.7.0.5 maintenance release.

#4 Updated by O'Neil Delpratt over 4 years ago

  • Sprint/Milestone set to 9.7.0.5

#5 Updated by O'Neil Delpratt about 3 years ago

  • Applies to branch trunk added
  • Applies to branch deleted (9.8)

#6 Updated by O'Neil Delpratt about 3 years ago

  • Fix Committed on Branch trunk added
  • Fix Committed on Branch deleted (9.8)

Please register to edit this issue

Also available in: Atom PDF