Project

Profile

Help

Bug #3423

closed

Incorrect binding to modes by name

Added by Michael Kay over 6 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
XSLT Conformance
Sprint/Milestone:
-
Start date:
2017-09-02
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
0.9, 1.0, Trunk
Fix Committed on JS Branch:
Trunk
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

Test override-v-015 demonstrates a problem with the binding of modes by name.

The initial mode is found by searching all mode components to find the first with a matching name. This is incorrect: it should always find a mode in the top-level package. Fixed this by using the same logic for finding the initial mode as we currently use for the initial function and the initial template.

This demonstrates another issue (which may be symptom-free): the index of modes (by name) held in context.fixed.modes is wrong in principle, because there can be several modes (in different packages) with the same name.

The same is true of the other indexes in context.fixed, such as context.fixed.globalVars and context.fixed.userFunctions.

Please register to edit this issue

Also available in: Atom PDF Tracking page