nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

text area editing issue

srilu

Hi,

Can any one solve below issue.

I created a DCR with tabs.

In first tab, i put one item with radio buttons on and off

In the second tab, i put one text area.

If i select "on" in the first tab, text area with tinymce editor will be visible.

If i select "off" in the first tab, normal text area will be visible.

The functionality is working fine.

But problem is,

When i click on "off", and trying to add content in the text area, cursor is not present in the text area, the cursor is coming on the DCT description (cursor is coming some where on the top, it's not coming in the text area).

When click on the top most bars of DCT, and then if click on the text area then i can able to enter data into text area.

But working fine when i select "on" in the first tab.

It's not working when selected "off".

Thanks in advance

Find more posts tagged with

Comments

Adam Stoller

I assume the second tab actually has two textareas, one with TinyMCE and the other without, and that you are using FormAPI to hide / expose one or the other based on the radio-button selection on the first tab - yes?

If so - perhaps you have an error in the FormAPI code - or perhaps its a more subtle issue:

ravisankar

Hi Ghoti,

Yes the way you said was the way we did it.

I tried some of the ways you stated. But they didnt work.
And the same formAPI code is working fine for another template with same functionality but name of tabs and items changed. So i guess its not our js api issue.

And I tried all posible ways that you suggested below nothing worked.

Still need to try container idea. Let me know if any ideas, mean while, I will update you after placeing containers

Thanks,
Ravi Sankar

ravisankar

Hi Ghoti,

I forgot to say, At the time i move to second tab and try to add content i was not able to, even if i go to other tabs in text and text areas i am not able to add. But if i change any radio buttion item then if i got to second tab into our non rich text field then i am bale to.

Finally if I come from forminit and then try to add this issue occure.

Thanks,
Ravi Sankar K.

ISCBorisB

The way I see it, you have two choices with the Forum.

You may attach your DCT/FormAPI code, perhaps stripped down to include only problematic components you've
described. That will allow us to (try to) replicate the issue, see what's wrong and propose fixes.

Alternatively, you may continue in this "my code does not work. Do you know why?" fashion.
Although it is still possible to provide some help (guidance, rather) even in this case, it is
agonizingly slow and requires inhuman patience which very few have (I certainly don't). Your choice...

For your own debugging, I would propose to start by temporarily commenting out every and all FormAPI. Sure,
you will have both Editing options visible and all that. Are they both operational and behave the way you expect?
If they are not, your problem may be compatibility, Browser itself or Browser's JVM Plug-in you are using
and so on. If they are, start carefully adding FormAPI pieces, checking functionality after each incremental
step. Sooner or later, you'll get the culprit...

Migrateduser

I second the post above. Just to give you a head start on some ways of finding the culprit:

Set both methods to be normal text, and then both to tinyMCE. This will isolate the states of change in your code, and you can then assess if it's a problem with your "views" (textAreas) or the "controller" (the code you use to change states).

As a last resort, don't shy away from using alerts. Hack into the objects in play, and output attributes. So you don't feel like you're wasting your time, save the snippet of JS as a "reporting" stub that can debug DCT items. This is a valuable thing to have.

As to the above poster's other point: people here aren't going to be interested in any sensitive information your code may contain. Isolate the buggy stuff and post it here so we can attack the problem instead of trying to guess at the innards of a black box.