|
Post by Everton on Nov 18, 2017 17:26:59 GMT -5
|
|
|
Post by sirfredrico on Mar 1, 2018 0:22:12 GMT -5
|
|
|
Post by budgall on Mar 1, 2018 1:27:19 GMT -5
Good job re-posting Everton's post of 3 months ago, did you something to add? Chrome's current version is 64.0.3282.
|
|
|
Post by jholland1964 on Mar 1, 2018 9:37:39 GMT -5
Good job re-posting Everton's post of 3 months ago, did you something to add? Chrome's current version is 64.0.3282. This thread yes is 3 months old but it is about Firefox. This was about a very temporary problem some folks had with the Firefox version 57 at that time. All problems were fixed and Firefox current version is now at 58.0.2. budgall-I have no idea why Everton's post would need to be re-posted either, especially when the problem was fixed by Mozilla 3 months ago.
|
|
|
Post by budgall on Mar 1, 2018 15:46:05 GMT -5
I knew it was about Firefox, but for some unknown reason I posted current Chrome version instead of current Firefox version. I was really questioning the reopening of a 3 month old post about a problem fixed long ago.
|
|
|
Post by jholland1964 on Mar 1, 2018 19:06:51 GMT -5
I knew it was about Firefox, but for some unknown reason I posted current Chrome version instead of current Firefox version. I was really questioning the reopening of a 3 month old post about a problem fixed long ago. I figured that. I too wonder about the reopening of a thread whose problem was fixed long ago too.
|
|
|
Post by sirfredrico on Mar 3, 2018 10:30:54 GMT -5
Good job re-posting Everton's post of 3 months ago, did you something to add? Chrome's current version is 64.0.3282. did i do that? lol.... i do remember reading it but didnt know i reopened it. mustve been falling asleep and clicked on post. lol
|
|