FLUID-5717: Merge policies contributed via dynamic grades do not operate correctly

Metadata

Source
FLUID-5717
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2015-07-27T11:42:31.041-0400
Updated
2017-02-27T15:49:12.500-0500
Versions
  1. 1.9
Fixed Versions
  1. 2.0
Component
  1. Framework

Description

Merge policies which are contributed from dynamic grades do not act in time to be seen by dynamic raw grade computers. This was discovered during testing of the FLUID-5249 branch, particularly with respect to the new FLUID-5241 contextAwareness scheme.

We have:

fluid.defaults("demo.prefsEditor.progressiveEnhancement", {
gradeNames: ["fluid.contextAware"],
contextAwareness: {
textToSpeech: {
checks: {
supportsTTS: {
contextValue: "{fluid.supportsTTS}",
gradeNames: "demo.prefsEditor.auxSchema.speak"
}
}
}
}
});

Which is then constructed via

var prefsEditor = fluid.prefs.create(".flc-prefsEditor-separatedPanel", {
build: {
gradeNames: [
"fluid.prefs.auxSchema.starter", // this will add the starter set
"demo.prefsEditor.auxSchema.simplify", // this will add the simplify adjuster and enactor
"demo.prefsEditor.progressiveEnhancement" // progressive enhancment
],
primarySchema: demo.prefsEditor.primarySchema
}
});

The mergePolicy of

mergePolicy: {
contextAwareness: "noexpand"
},

is not seen when fluid.contextAware.check executes as part of the raw dynamic grade resolution.

Comments

  • Antranig Basman commented 2015-08-20T10:08:18.029-0400

    Merged into trunk at revision 282f1a318718eed0b0ec060fb8b4ad254417fd7e