April 2, 2019 at 8:31 am
In Chrome, I see the bullets. v72.0.x
April 2, 2019 at 2:24 pm
I'm seeing bullets now.
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
April 2, 2019 at 2:26 pm
The old forum used to BOLD threads that had unread posts/replies and it also had a link to take you directly to the last unread post. It's much harder to find unread posts without this functionality.
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
April 3, 2019 at 10:58 am
Sean - I don't think we're going to be able to stop Firefox autofilling any time soon. Recent versions are ignoring autocomplete="new-password"
and autocomplete="off"
standards that ask the browser not to autofill forms. We'll leave it in place in case it's a bug in recent builds - if they start acknowledging it again it should go away.
April 3, 2019 at 11:43 am
Sean - I don't think we're going to be able to stop Firefox autofilling any time soon. Recent versions are ignoring
autocomplete="new-password"
andautocomplete="off"
standards that ask the browser not to autofill forms. We'll leave it in place in case it's a bug in recent builds - if they start acknowledging it again it should go away.
Seems it's documented behaviour, interestingly Dave:
...many modern browsers do not support
autocomplete="off"
for login fields:
- If a site sets
autocomplete="off"
for a `</em></em><form>`, and the form includes username and password input fields, then the browser will still offer to remember this login, and if the user agrees, the browser will autofill those fields the next time the user visits the page.</form>
- If a site sets
autocomplete="off"
for username and password<input type="text" />
fields, then the browser will still offer to remember this login, and if the user agrees, the browser will autofill those fields the next time the user visits the page.This is the behavior in Firefox (since version 38), Google Chrome (since 34), and Internet Explorer (since version 11).
The page does go on the then discuss autocomplete="new-password"
:
If you are defining a user management page where a user can specify a new password for another person, and therefore you want to prevent autofilling of password fields, you can use
autocomplete="new-password"
; however, this is a hint for browsers so they are not required to respond to it.
Underline for emphasis.
Edit: Seems that underlining is no longer working. When pressing Ctrl+U
. <span style="text-decoration: underline;">Example</span>. Edited the above (which is now underlined) to use BBCode.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
April 3, 2019 at 1:44 pm
I had a feeling it was a browser issue. Interestingly FF does not ask to autofill, it just does. Strange behavior since it doesn't do that elsewhere.
Thanks for the update Dave. And thanks for all the work you guys are doing to fix the bugs as they popup.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
April 3, 2019 at 1:45 pm
Yeah, it's also not lost on me that the best documentation on it comes from Mozilla themselves. Until very recently they supported autocomplete="new-password"
. Not sure why they stopped, but I think we might be on a losing streak trying to fight the behaviour the browser maker wants.
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply