Rendering of select widget in Internet Explorer

[Neil Griffin]

I have been happily running my wiki in Firefox but recently in preparing to make it ready for others to use, I tried it in Internet Explorer and found a problem with the way the select widget gets rendered.  Everything I describe works fine in Firefox, Chrome and various Android browsers as far as I have seen.

The problem can be seen most simply when just using a normal select widget connected to a field in the current tiddler.  In this case, when you select an option, unless it is the first option in the list, the selected text appears momentarily and then vanishes, concealing the selected option.  This can be fixed by connecting the widget selection to a field in a different tiddler instead of the current one.  This is workable, if slightly annoying.  Having siad that, if in a single tiddler you have one select widget connected to the current tiddler and one connected to another tiddler, using the one connected to this tiddler breaks the one connected to another tiddler. See demo (obviously use IE to see the problem):
http://ng110.tiddlyspot.com/#select%20widget%20problem%20demo

I am using a slightly more complicated setup using a javascript macro to connect two select widgets together so that the set of options in one depends on the selected value in the other.  I use this to provide selection for 'minimum' and 'maximum' where it is not possible to select a combination where max<min.  Unfortunately, when I use this, even if the select widgets are connected to a field in another tiddler, the disappearing selection problem comes back. Demo:
http://ng110.tiddlyspot.com/#Min%2FMax%20columns%20demo

Any ideas on how this might be fixed (or circumvented)?

Thanks,

Neil.

[PMario]

I don't have a solution, but I can confirm, that there is a problem with IE 11 win 8.1
-m

[Jeremy Ruston]

Hi Neil

> This can be fixed by connecting the widget selection to a field in a different tiddler instead of the current one.  This is workable, if slightly annoying.

Just as with the edit-text widget, I'd recommend not using the select widget on the tiddler that contains it. The trouble is that changes to the tiddler value will trigger a refresh of the content containing the select widget. Some of the interactive state of the select control (eg whether it is dropped down or not) cannot survive the delete and recreate cycle of a refresh. I suspect that that's what going on in IE.

Best wishes

Jeremy.

On Fri, Apr 3, 2015 at 10:40 PM, PMario <pmar...@gmail.com> wrote:

I don't have a solution, but I can confirm, that there is a problem with IE 11 win 8.1
-m

--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/44d59cda-d9df-4fa0-9fa9-ca8b434a6372%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Neil Griffin]

I thought it might be related to the edit-text problem.

For my linked select widgets, although each widget is connected to a field in another widget, those values are transcluded back into the current tiddler as inputs to my macro, which in turn rewrites the select widget, no doubt causing them to refresh.

However, the real question is why Internet Explorer chooses to show a blank box when it refreshes, rather than the current value of the field, unless the selected field corresponds to the first item in the option list.  Using a default value doesn't fix this.  Do we have to write this off as bizarre IE behaviour, or is there something TW can do to force it to show the selected option on refresh?

Neil.

[Neil Griffin]

Okay, so I found a fix for my linked widgets.  Since my macro is writing out the option tags each time, I can get it to add a 'selected' attribute to the currently selected option, and that forces it to display the correct option when the widget refreshes.

Fixed version demonstrated here: http://ng110.tiddlyspot.com/#Min%2FMax%20columns%20demo

Neil.