News:

Bored?  Looking to kill some time?  Want to chat with other SMF users?  Join us in IRC chat or Discord

Main Menu

Missing input field

Started by Sir Osis of Liver, August 20, 2021, 12:44:34 PM

Previous topic - Next topic

Sir Osis of Liver

Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Sir Osis of Liver

#1
Dropmenu is displayed in IE, not in FF.  All other dropmemus in Server Settings display correctly in FF.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Antechinus

Quote from: Sir Osis of Liver on August 20, 2021, 11:13:38 PMDropmenu is displayed in IE, not in FF.  All other dropmemus in Server Settings display correctly in FF.
No idea what you mean by this. All drops work AFAICT.

Sir Osis of Liver

I'm running FF82, all dropmenus in server settings display correctly except for that one.  I have all security/privacy settings maxed, running Ghostery and JS Toggle (it's on), but if it were any of those all dropmenus should be affected.  Must be something different about cookie length menu.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Antechinus

All drop menus are working fine, as far as I can tell. Are you talking about a select? If you are talking about a select, that is not a drop menu.

The drop menus are the things that drop down off the various menu bars. Html select elements are completely different elements. Don't go confusing them. It just makes it more difficult to figure out what you are trying to say.

Also note that a select is not an input field either. Input fields use the input tag, not the select tag. If this is about a select, the thread title is only going to confuse things.

And why are you running FF82, when 91 is the current version? The select in question (I assume that's what this is about) displays perfectly in FF91. I'm running an "RC4" build, taken straight from GitHub a couple of days ago.

Sir Osis of Liver

Posted a screenshot, whatever it's called you can see it's missing.

I stopped upgrading FF at 81 because last upgrade caused reset, lost all settings and bookmarks.  If everything worked like it's supposed to, I'd have more hair.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Antechinus

You can save your existing bookmarks and import them into any version of FF. ;)

Sir Osis of Liver

Yes, I did that.  It also saves them when FF resets, but it's a pia to restore them, moreso to reset all the settings.  I don't run anything with default settings.  Don't think this glitch has anything to do with FF version.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Arantor

Does it work if you turn off Ghostery/JS Toggle and run with the browser as actually intended? I'm wondering if Ghostery has some rule in it that thinks the dropdown should be hidden.

(Also, dropdown to mean dropdown selector was a term that predates SMF by some years.)

Sir Osis of Liver

Ghostery is blocking it, but only that one, all others are displayed normally.  Must be something different about it.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Arantor

I think it doesn't like the names 'globalCookiesDomain' and 'cookieTime' on the theory that they're privacy-busting somehow.

I don't think this is something SMF should fix since changing this affects either the template (and thus half the admin panel), or very, very careful renaming of just those elements (and then making sure the correct values get routed to the correct variables) - or just whitelist forums you're running...

Sir Osis of Liver

Must be very picky, never blinked at "cookielength".  Not a problem for me, it defaults at "forever", which is what I use on my forums, and most of my guys prefer.
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Arantor

Except that your screenshot is missing the cookieTime field as well as the globalCookies field, so clearly it's not happy about *something*. But I'm guessing it's because it's a non-checkbox that contains the word cookie, for 'privacy'. This is why I ended up ditching Ghostery and switching to uBlock Origin because Ghostery kept breaking things for 'privacy' that I'd actually prefer it didn't.

Advertisement: