xsd:Name atom is defined with wrong case (xsd:name), part 2

RESOLVED FIXED

Status

Core Graveyard
XForms
RESOLVED FIXED
12 years ago
2 years ago

People

(Reporter: Steve Speicher, Unassigned)

Tracking

({fixed1.8.1})

Trunk
fixed1.8.1

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

1.00 KB, patch
Doron Rosenberg (IBM)
: review+
beltzner
: approval1.8.1+
Details | Diff | Splinter Review
(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

Looks like my testing with just:
  <xforms:bind nodeset="." type="xsd:Name"/>
didn't expose another use of wrong "name", see:
  http://lxr.mozilla.org/seamonkey/source/extensions/webservices/schema/src/nsSchemaSimpleTypes.cpp#185
problem it occurs when I rely on external schema for node validation types.

This is a follow-on to bug 348889


Reproducible: Always
(Reporter)

Comment 1

12 years ago
Created attachment 234250 [details] [diff] [review]
patch
Attachment #234250 - Flags: review?(doronr)

Updated

12 years ago
Attachment #234250 - Flags: review?(doronr) → review+

Updated

12 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

12 years ago
fixed on trunk
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED

Comment 3

12 years ago
Comment on attachment 234250 [details] [diff] [review]
patch

This has no risk and will only affect XForms and Webservices (of which I am
module owner these days), and would be great to have in 1.8.1
Attachment #234250 - Flags: approval1.8.1?
Comment on attachment 234250 [details] [diff] [review]
patch

a=beltzner on behalf of drivers, please land on MOZILLA_1_8_BRANCH and mark fixed1.8.1
Attachment #234250 - Flags: approval1.8.1? → approval1.8.1+

Comment 5

12 years ago
thanks for the fast approval!
Keywords: fixed1.8.1
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.