I'm of the opinion that the Firefox port was updated to 47 very
prematurely. Even though the SVN commit note says it was a release
candidate, I don't usually look at commit notes when I've updated my
ports tree and ran into some weird issues with 47 that made me downgrade
back to 46.0.1. 47's official release isn't until tomorrow.
Thanks,
Naram Qashat
On 2016-06-06 14:21, Bob Willcox wrote:
I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when
I go
out to cnn.com it hangs, eventually putting up a dialog box telling me
that a
script has stop working (or something similar). Nothing I've tried so
far
seems to help and I wind up having to kill firefox.
Anyone else experiencing this? Not that other sites (besides cnn.com)
have
hung on me as well, but cnn.com seems to be the worst (fails the
quickest,
within seconds of going there).
--
Bob Willcox | Which is worse: ignorance or apathy?
b...@immure.com | Who knows? Who cares?
Austin, TX |
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
"freebsd-ports-unsubscr...@freebsd.org"
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
