Possible bug with IE8 and customfield categories

Hi,

I have a strange behavior with RT 3.8.7 but I think it’s the same
with newer versions.

I create a ticket with customfields and categories of customfields. I
set a customfield named “CF_A” in a “Select one value” field. I have
then a list of values available for “CF_B” custom field, I select one,
fine.

In the display view, I have both CF set. When I click “Basics”, CF_A
and CF_B are correctly set on Firefox 4 and Chrome 10. On IE8, only
CF_A is set, but CF_B is “none”.

Do you have the same problem or do I have something wrong on my side?

Many thanks,
L.B.

Hi,

I have a strange behavior with RT 3.8.7 but I think it’s the same
with newer versions.

I create a ticket with customfields and categories of customfields. I
set a customfield named “CF_A” in a “Select one value” field. I have
then a list of values available for “CF_B” custom field, I select one,
fine.

In the display view, I have both CF set. When I click “Basics”, CF_A
and CF_B are correctly set on Firefox 4 and Chrome 10. On IE8, only
CF_A is set, but CF_B is “none”.

Do you have the same problem or do I have something wrong on my side?

This sounds familiar, and may be related to this bug that Emmanuel has
been hacking on:

http://issues.bestpractical.com/Ticket/Display.html?id=16629&user=guest&pass=guest

This patch hasn’t yet made it in as a branch or a commit but if you
can test it, it might help him.

-kevin

This sounds familiar, and may be related to this bug that Emmanuel has
been hacking on:

http://issues.bestpractical.com/Ticket/Display.html?id=16629&user=guest&pass=guest

This patch hasn’t yet made it in as a branch or a commit but if you
can test it, it might help him.

-kevin

Hi Kevin,

I would be happy to test, but I think there is no patch to test, or
did I miss something ? Emmanuel says he couldn’t fix it, I tried as
well without luck.

I don’t see any patch in the link above :frowning:

L.B.

This sounds familiar, and may be related to this bug that Emmanuel has
been hacking on:

http://issues.bestpractical.com/Ticket/Display.html?id=16629&user=guest&pass=guest

This patch hasn’t yet made it in as a branch or a commit but if you
can test it, it might help him.

-kevin

Hi Kevin,

I would be happy to test, but I think there is no patch to test, or
did I miss something ? Emmanuel says he couldn’t fix it, I tried as
well without luck.

I don’t see any patch in the link above :frowning:

Looks like Emmanuel did it as a comment, I’m not sure if that was
intentional or not, but I’d re-added it as a reply so you can see it
and give it a look. This isn’t considered an official fix in any
sense of the word, just some exploratory bugfixing by elacour

-kevin

I don’t see any patch in the link above :frowning:

Looks like Emmanuel did it as a comment, I’m not sure if that was
intentional or not, but I’d re-added it as a reply so you can see it
and give it a look. This isn’t considered an official fix in any
sense of the word, just some exploratory bugfixing by elacour

I tried it and it works, many thanks to Emmanuel !

L.B.

I don’t see any patch in the link above :frowning:

Looks like Emmanuel did it as a comment, I’m not sure if that was
intentional or not, but I’d re-added it as a reply so you can see it
and give it a look. �This isn’t considered an official fix in any
sense of the word, just some exploratory bugfixing by elacour

I tried it and it works, many thanks to Emmanuel !

you’re welcome :wink: