MenuBar & IE8

Hi guys !

I’m on the final run to the end of my project… At least ! Still two weeks to my deadline - and then I’ll be able to, err, do all the things I said I’ll do ^^’
Sorry for being quite a ghost here, only coming to ask questions…

Anyway, I’ve got one last thing to ask :slight_smile:
Everything more or less work… Apart from a strange, strange thing.

I use the MenuBar component in my project. I’ve no real workaround, I truly need that component, and it’s too late to change it for something else.
In Firefox & Opera, no problem.
But in IE7 !

Even when I’m using the ticket source code (com.itmill.toolkit.tests.tickets.Ticket1598.java), nothing appear with that cursed browser ! I do not even have an error… Not even a blanck space ! The component is not rendered, there is just… nothing.

Do you have any idea on why that happen, and on what I can do to fix it ?

I’ve looked a bit in the source code, but I saw nothing that can explain the IE stubborness to render it. It’s as IE doesn’t even try to display the MenuBar !

Thanks a lot for everything,

Quentin.

I tested MenuBar with Windows XP and IE&IE7 and both worked fine with the current Toolkit version. What version of the Toolkit do you use?

Judging from the topic, you probably mean IE8. IE8 is still in beta so support for it is not complete, but I’ll see what I can do.

EDIT: I tested IE8 Beta 2 with Windows XP SP2, and it worked surprisingly well. I tried the Ticket source code and found nothing suspicious. So back to the original question: what kind of a configuration are you running?

Whoops, no, it’s an error from me in the title, I meant IE7.

And, well…

Just ignore that topic :expressionless:
I must be tired… I thought I was using the latest build version, but I was not.
Using the true last one correct that bug.

It does cause some regressions in other parts of my apps, but well… That’s the game ^^’

Quentin.

And for that we’re genuinely sorry!

We’re always trying to minimize the chance for regressions between releases, but due to the current state of development and non-stableness, it’s virtually impossible :frowning: The stable 5.3 is getting close, though!

You might not have time for this at this time, but if you do, it would be really interesting to hear what issues you encountered, and which were worst - perhaps we can avoid them better in the future.

Good luck with the deadline, try not to stress too much!

Best Regards,
Marc

No prob for the (quite small) regressions :slight_smile:

The only one that is annoying me is a page that throw an InternalError straight to my face… But, well, I must be doing something wrong ^^

Quentin.

Ahah

It seems that the InternalError came from… the CellStyleGenerator :smiley:
Yeah, the one and only patch I’ve commited…

Commenting the whole block solve the error, that’s good enough for now :smiley:

Quentin.