We've been here before with Fluid Dynamics. The whole rational
explanation/discussion thing didn't work last time, and probably won't
this time.
I'd suggest ending this thread immediately.
Timothy Baldridge <tbaldri...@gmail.com> writes:
> To expand my previous reply. What site are you talking about? I got your
> email via my email client (Gmail) so what are you talking about?
>
> And if you are talking about the Google Groups website, perhaps contact
> them? This is completely the wrong place to complain about how your browser
> reacts to some site's view of a mailing list. This list has 0 control over
> whatever site it is that you use, so complaining here not only is
> pointless, but is also just spam.
>
> Timothy
>
> On Thu, Oct 8, 2015 at 9:09 AM, Timothy Baldridge <tbaldri...@gmail.com>
> wrote:
>
>> lol, wut?
>>
>> On Thu, Oct 8, 2015 at 9:06 AM, Fluid Dynamics <a2093...@trbvm.com> wrote:
>>
>>> I don't know what you guys did, but as of about 2 days ago, when browsing
>>> this site about 1 time in 20 after reading an article and then clicking
>>> "back" to go back to the topic list my main Firefox window disappears and
>>> is replaced by a small dialog with two options, "restart Firefox" and "quit
>>> Firefox". I DON'T WANT TO DO EITHER. I WANT TO GO BACK TO THE TOPIC LIST.
>>> THAT IS WHY I CLICKED THE "BACK" BUTTON AND NOT THE "RESTART OR QUIT"
>>> BUTTON.
>>>
>>> Whatever alterations you have made to this site a few days ago, you are
>>> to un-make immediately. Hijacking your site's viewers' browsers is NOT
>>> acceptable under ANY circumstances. If you have not restored the previous
>>> behavior ("back" button behaves exactly as advertised, 100% of the time) in
>>> three (3) days (so, by Monday morning), I will quit using this site and
>>> recommend to everyone I know -- friends, everyone I work with, bosses, etc.
>>> -- that they avoid this site due to browser hijacking behavior.
>>>
>>> I recommend you simply retrieve the site's code as it existed a week ago
>>> from your backup tapes (you DO keep backups, right?) and replace the
>>> currently running web-app with this older version. The version of a week
>>> ago lacked the objectionable browser hijacking behavior. It shouldn't take
>>> you more than 30 minutes. Assuming you did your due diligence and kept
>>> proper backups, especially making them before introducing changes that
>>> could have major repercussions. That makes the three-day deadline quite
>>> generous.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
