OK, i employed this technique in this commit,

https://github.com/chrispetsos/prefsEditors/commit/bbcd7b42035fc9d48a3d255dd3af663924c0cc68

Basically, what i had to do was to give each preview frame a unique selector and add that "arrayMergePolicy" to "selectorsToIgnore".
Could you check if you still have the bug with the previews?

Date: Fri, 25 Oct 2013 07:38:52 -0700
From: notifications@github.com
To: prefsEditors@noreply.github.com
CC: chrispetsos@msn.com
Subject: Re: [prefsEditors] GPII-187, GPII-188, GPII-225, GPII-227 contributions (#7)

In src/pmt/js/PMT.js:

> +                },
> +                resetButtonText: {
> +                    expander: {
> +                        func: "gpii.uiOptions.pmt.lookupMsg",
> +                        args: ["{uiOptionsLoader}.msgBundle", "resetButtonText"]
> +                    }
> +                },
> +                cancelButtonText: {
> +                    expander: {
> +                        func: "gpii.uiOptions.pmt.lookupMsg",
> +                        args: ["{uiOptionsLoader}.msgBundle", "cancelButtonText"]
> +                    }
> +                }
> +            },
> +            components: {
> +                increaseSizeExtraAdjustersComponent: {

Another thing that might help is that your container specification for the previews should use a selector derived from the parent. So you could just set the container like {that}.dom.cursorSizePreview or something like that. Right now by specifying it like ".flc-uiOptions-cursor-size .flc-uiOptions-preview-per-setting-frame" causes it to look through the entire page and not just within it's parents scope.


—
Reply to this email directly or view it on GitHub.