+1 Jive bug: Jived up page and "next" buttons COMPLETELY broken

[#1]

Yep, I'm on another Adobe forum right now, clicking "Next" (both the top and bottom link), and clicking page "2".  They all do the same thing-- it scrolls to the top of the screen, and STAYS on page 1.

Meanwhile, THIS forum works perfectly fine, both next and page links.

Chrome 2.0.172.33

"Google Chrome is up to date", it says. A simple page link should work.

But even if it wasn't up to date, this inconsistent and seemingly random behavior of JiveJax (Jive's garbage implementation of Ajax) is completely buggy and not production worthy.  Not production worthy, even in a Dunkin Donuts web discussion forum.  Heck, even more irrelevant and useless--not production worthy of being used as forum software for Congress!

So is this a new bug, or has it also been reported 50 times?  Funny that ever since I decided to stop ignoring weird stuff like this (page reloads tend to fix this stuff), posting bug reports instead (perhaps I should just say just posting here instead, since Adobe isn't reading any "reports"), I've noticed the bug count pile even higher than I would have imagined in such a short time.  It's like I just learned to tune out all the weird stuff, hit reload, and move on.  Is this really how it's supposed to be?

Yep, a reload of the page fixed it. Wow..

[#2]

Yep, I'm on another Adobe forum right now, clicking "Next" (both the top and bottom link), and clicking page "2".  They all do the same thing-- it scrolls to the top of the screen, and STAYS on page 1.

Meanwhile, THIS forum works perfectly fine, both next and page links.

Chrome 2.0.172.33

"Google Chrome is up to date", it says. A simple page link should work.

But even if it wasn't up to date, this inconsistent and seemingly random behavior of JiveJax (Jive's garbage implementation of Ajax) is completely buggy and not production worthy.  Not production worthy, even in a Dunkin Donuts web discussion forum.  Heck, even more irrelevant and useless--not production worthy of being used as forum software for Congress!

So is this a new bug, or has it also been reported 50 times?  Funny that ever since I decided to stop ignoring weird stuff like this (page reloads tend to fix this stuff), posting bug reports instead (perhaps I should just say just posting here instead, since Adobe isn't reading any "reports"), I've noticed the bug count pile even higher than I would have imagined in such a short time.  It's like I just learned to tune out all the weird stuff, hit reload, and move on.  Is this really how it's supposed to be?

Yep, a reload of the page fixed it. Wow..

[#3]

BY THE WAY. Here's a little bit of interesting information. I just had to try posting this message THREE times before it went up. The first two times it said:

"An unexpected error has occurred"

(and that was it, blank white space below)

I'm lucky the auto-recovery feature worked to bring the post back. Now I see why Jive implemented it-- it lets you recover from all of the other bugs.

+1 Jive bug, again.

[#4]

Damn do I miss Dunkin' Donuts.

The next and page number buttons work fine in Safari.  Maybe you need to switch to a less standards compliant browser.

[#5]

what jesse said.

[#6]

It's all about the Boston Kreme...

[#7]

Reporting  bugs on unsupported browsers is not helpful to the forums. IF anyone is attempting to use the forums to track bugs for fixing, then you are making their job more difficult. I get it, you like Chrome. If its not supported and causes issues, then it is your problem and not Jive's nor Adobe's. I use an unsupported program. I use NetNewsWire on a Mac. It causes me fewer issues than Safari. Strangely, it is based upon the same Webkit that Safari uses. Go Figure. However, if it caused more issues, then it would be my problem not Adobe's. I do use several browsers and different OSs depending upon the task and application I need to use. It is my problem to use a supported system, not the other way around.

[#8]

The problem here is that the "unsupported" browser is the only browser I can get this crap working correctly on.  Kind of funny huh?  I can't install anything else here and IE is way, way too slow.  Even if I could use Opera, I already know this Jiveing text input box does all kinds of strange things in that browser.

So that's three browsers, three that aren't working correctly with Jiveware. Huh? Did someone remember to check whether Jive supports the Internet?  I'm not sure it does.

And I thought someone said "Safari sucked"? So now I have to switch to "teh suck" browser to use "teh suck" forums... I guess that would be fitting.

[#9]

i don't have any problems with firefox 3.0.10, firefox 3.5, ie 6, ie7 or ie8.

sounds like you've got a classic PEBCAK error to me!!!

[#10]

Reporting  bugs on unsupported browsers is not helpful to the forums

sorry mike if i missed it... where is the official "not supported" browser list? i thought that was a joke someone was tossing around here... you can't really be serious that adobe doesn't support a fully (or nearso) w3c compliant browser...?

[#11]

dave milbut wrote:

i don't have any problems with firefox 3.0.10, firefox 3.5, ie 6, ie7 or ie8.

sounds like you've got a classic PEBCAK error to me!!!

Har, har. I wish it were that simple. And no, it's not an "8th layer problem" either. I can't use Firefox here, and honestly IE just sucks in more way than one. The slowness may be due to the crap workstation I have for interwebbing (sad that IE is that much slower than Chrome that it's unusable here), but none of this can be altered for the time being. Chrome is pretty much my only choice here. I'm lucky to have that even.

[#12]

I can use FireFox 3.5 just as well as SeaMonkey 1.1.17, or Safari 4.0, or ever Opera 9.64 But usI e Mac Platform. maybe its a OS issue so far as some of the browsers go.

[#13]

Why won't FF/SM work? is it it simply won't work on your machine. Or the company your work for doesn't allow it?

[#14]

Between you and Ansury the list of not support browsers has been posted.

[#15]

what browsers are supported you've rulled out FireFox, Safari,Chrome, SeaMonkey, IE 5/6/7/8, OmniWeb, Opera, iCab, Konqueror. What else is there left.

[#16]

PjonesCET wrote:

what browsers are supported you've rulled out FireFox, Safari,Chrome, SeaMonkey, IE 5/6/7/8, OmniWeb, Opera, iCab, Konqueror. What else is there left.

hehehehe

IE4?

And this is exactly the problem with JIVEware.

So there's a list somewhere? Any free links available for the lazy?

Anyway, I'm glad that my unsupported browser works with Jiveware 99% of the time, at least. If only the "supported" browsers did, too...

[#17]

Smoke signals

[#18]

Just trying out OmniWeb.

After making a copy of my userContent.css file (created with help from someone this Forum for SeaMonkey and FireFox) and placing in a data folder and setting up as a custom Userscript for site then pointing to copy, looks as good as in FireFox or SeaMonkey.

Now tried with iCab. Works fine as well.

Message was edited by: Phillip Jones @ 6:25 EDT

Now  finally tried with Safari 4 as well.

Message was edited by: Phillip Jones @ 6:30 EDT

[#19]

Now back to SeaMonkey.

It appears that I can get to forum, and other than the normal bugs (not counting this chrome problem) I can use forum just as well with:

SeaMonkey

Safari

Firefox

iCab

OmniWeb   

Opera.

Ansd it appears in all of these I don't have the problem described above about the chrome type bug

[#20]

PJ when you use Opera, does your clipboard and return key work correctly in the text box?  Can you cut/paste text and or add new blank lines and have them go into the correct location?

I think I am on a slightly older version of Opera at home (probably 9) so that could be the issue there (well, it's still not excusable for Jive, but at least it would be a fix).

Or, are you telling Opera to mask or identify as another browser like IE or FF?  I think I had the best results masking as FF but still had a few text entry issues that were just terrible.

[#21]

Yes return key works just fine.  and clip board seem okay.

Used

Opera 9.64.5270

OmniWeb was 6.2.622.6.1.0.111015

iCab was 4.6.1

Safari 4.0.

No I let it identify automatic which means it identifies itself as 9.64

One of the identities it could use is FireFox 3.0.

[#22]

Okay, different version, I have Opera 9.51.

(Which you would think, isn't so different, but not according to JiveWare©.)

[#23]

Good news, everyone!

I just saw the same exact thing happen in Opera, too!  So it's not a Chrome specific problem, it's just a major bug in the forum software itself!

</farnsworth>

Again, reloading the page fixed it.  Also the initial page only had a link for pages 1 and 2 (which didn't work at all), but when I reloaded I ended up with links up to page 5, which worked.

+1 LAME JIVE BUG

[#24]

Great detective work!

try OmniWeb if your on Macintosh, or see if they have a windows version.  or try Windows version of Safari if on Pc and see if you can get it to reproduce on those.

[#25]

I'm tired of trying new browsers, I'll make do with Opera and Chrome....IE if it's the last resort.  Jive sucks so bad...

[#26]

I'm tired of trying new browsers,

then you SHOULD be using firefox!

[#27]

dave milbut wrote:

then you SHOULD be using firefox!

Dave...

Why should one be using anything in specific...? They should all effing work! Whether IE 5 or 99... FF 1 or 99... Safari 99 or 1... the basic fact remains that these are Public Foruns and should cater to all the browsers – ok... modification, all the popular, at least, browsers. Last count... IE 6 was still the most used browser of all. IE as a brand the most used – obviously – and FF in #2.

So all this crap about this browser and that is just Jive jerking everyone around because they have a product that doesn't work flawlessly with *any* browser.

'nuff said...

Cheers!

JJ

[#28]

If written to w3c standards its shouldn't make any difference what Browser is used, even any version of IE will accpet it.

[#29]

Why should one be using anything in specific...? They should all effing work!

well, ya. they SHOULD, but most don't. FF does. consistantly.

So all this crap about this browser and that is just Jive jerking everyone around because they have a product that doesn't work flawlessly with *any* browser.

no argument here.

[#30]

dave milbut wrote:

I'm tired of trying new browsers,

then you SHOULD be using firefox!

1) I'm not a firefox fanboy so I'm not going to use it if I find alternatives better, unlike some who will never switch because it's their new religion

2) I have enough browsers to begin with, and they all work fine on every other site on the Internet, forums especially

3) I just don't like firefox

4) I can't install firefox at work

5) I recall seeing complaints about things being broken in Jiveware for firefoxians too, so I don't see the point

6) If JiveS**t is my main reason for having to install firefox and I do install it, I'll just hate both of them more as a result (I bet you those Jives use FF for development, and test on NOTHING else other than to see if you can post a message in IE. lol)

That's why I shouldn't, so unless you have a longer and better list of reasons why I should, I think I'll stay away.

Come on Dave, do you really want to defend Jiveware like this? This was a joke wasn't it???

[#31]

Come on Dave, do you really want to defend Jiveware like this?

i wasn't aware i was defending jive.

This was a joke wasn't it???

yes. yes it was.

[#32]

so unless you have a longer and better list of reasons why I should, I think I'll stay away

how about it's at least 50% less evil?

[#33]

dave milbut wrote:

This was a joke wasn't it???

yes. yes it was.

Well, a little more captain obvious and a little less jiving around might prevent such misunderstandings! lol

[#34]

Ansury wrote:

dave milbut wrote:

This was a joke wasn't it???

yes. yes it was.

Well, a little more captain obvious and a little less jiving around might prevent such misunderstandings! lol

it IS obvious that firefox is the best browser out there!

[#35]

dave milbut wrote:

it IS obvious that firefox is the best browser out there!

+1 missing/crappy Jive feature: no <rolling eyes> smiley graphic! 

[#36]

If it works correct in FF/SM, because they are 98% W3C Standards Compliant and working on the other 2 %. Anything that will work in FF/SM will work in any other browser put out that comples with W3C standards. evn  IE 5.6.7 which have this crazy feature called self-healing . That allows them to accept code with missing tags by send the apropriate opening or closing tags  So that people that didn't know how to properly code in FrontPage would still have sites that works.

No browser should have self-healing feature. So that people writing the code would have to do it right to start with. Another Thing I'm not in favor of is Browser Sniffers.

My bank use browser sniffer in their code for their website. and have it to key on the word Fiirefox instead of on gecko. So in order to use SM I have to alter SM to work I have to type on end of useragent string /not firefox 2.0.

One works just as well as the other. both use identical code , just SM has email and newsreader as well. but engine for gecko is identical.

[#37]

I agree those 'extra' features are terrible, terrible, terrible.

Don't really agree that anything working on FF/SM should work on a 100% compliant browser, but nevermind.

[#38]

+1 missing/crappy Jive feature: no <rolling eyes> smiley graphic!

http://milbut.org/smilies/davesmileys.php

[#39]

there is no 100% compliant Browser, because the specfcations are always being updated or tweaked. FF/SM coms the closest. IE 8 is supposed to be up their pretty close  But its the obligation  of the site creator to get as close to specifications as possible. If you write code for a site so that it shows properly in FF/SM (Mozilla) then it should work in any browser that follows the same spefications. whether webkit, or Gecko, or any other modern engine.

[#40]

Used to be Opera, or at least so they claimed, so I'd check up on that fact. Of course some time has passed since I read that, and now it doesn't generate any revenue for Opera Software on the desktop since it's free...

Browser compliance is a boring topic anyway. Get back to bashing Jive!

[#41]

They only Browser you have to pay for on Mac platform is iCab and its just $20.00 for single user License.

Mozilla They don't cost anything other than time to download. How they make any revenue is Google pays or donates so much per hit/use when Google is used in FF/SM. now you can get a free version of iCab but in order to get rid of Nag screnn you pay the fee. OmniWEb is also free now.