Quick Reply "mask" ...
#1
Senior Member
Thread Starter
Quick Reply "mask" ...
Beginning yesterday evening (21Mar2019) the Quick Reply ¼ overlay/mask (for lack of a more betterer term) appears EVERY TIME, and not for just of the 1st occurence of a f150forum.com web session, whenever the View First Reply selection is -click-ed. Again ... This behavior started the evening of 21Mar2019.
Supplemental information:
.
NOTE: This is also the case, and occuring at www.ford-trucks.com (which also is a IB - Internet Brands site).
UPDATE: It is now happening (overlay/mask) when opening ANY thread, macht nichts whether View First Reply selection is -click-ed.
Supplemental information:
.
- situarion is the same regardless of browser - Firefox, Edge, IE
- there have been no desktop (Windows 10) or browser changes.
NOTE: This is also the case, and occuring at www.ford-trucks.com (which also is a IB - Internet Brands site).
UPDATE: It is now happening (overlay/mask) when opening ANY thread, macht nichts whether View First Reply selection is -click-ed.
Last edited by gDMJoe; 03-22-2019 at 03:48 PM.
#2
Senior Member
#3
We have literally no idea why this happened, as we didn't touch anything at all--it just broke. Should be fixed now.
#4
Senior Member
Beginning yesterday evening (21Mar2019) the Quick Reply ¼ overlay/mask (for lack of a more betterer term) appears EVERY TIME, and not for just of the 1st occurence of a f150forum.com web session, whenever the View First Reply selection is -click-ed. Again ... This behavior started the evening of 21Mar2019.
Supplemental information:
.
UPDATE: It is now happening (overlay/mask) when opening ANY thread, macht nichts whether View First Reply selection is -click-ed.
Supplemental information:
.
- situarion is the same regardless of browser - Firefox, Edge, IE
- there have been no desktop (Windows 10) or browser changes.
UPDATE: It is now happening (overlay/mask) when opening ANY thread, macht nichts whether View First Reply selection is -click-ed.
Its being blamed on my old OS but now i see you and possibly one other are having this issue using Windows 10.
#5
Mopar, his issue was stemming from a known issue that even us here in the office were seeing that we addressed, which is unrelated to your issue.