Moved up to 4.3.0 from 3.8.0 and experiencing this problem:
The method ‘setTitleAt is adding close buttons to tabs, even tabs that I’m not addressing, and even if the tab has this set:
I am getting multiple close buttons on a single tab. Every time the setTitleAt is called on a dynamically created tab, all the tabs get an additional close button.
Thank you for this feedback.
You’re welcome. I’m interested to know when this will scheduled to be fixed.
One other thing – when I make a posting here and it is replied to, I”m not receiving any email notification. I thought it was automatic since my email address is part o my profile. So how can I automatically receive updates to my postings?
Thank you for the interest.
We create a work item for this.
Unfortunately, no such option, to receive an e-mail.
An another alternative is to regularly check our Roadmap.
- This reply was modified 3 years, 4 months ago by Hristo.
Today 2/15/17 I upgraded to 4.5.0 and I am still seeing multiple ‘x’ to close tab on all the tabs I create. Regardless of whether they’re created in HTML or dynamically. AS I create more tabs dynamically they each get an added ‘x’. I have tabs with 5, 6, 7 ‘x’s.
I am stuck.
More — It happens every time I call the function setTitleAt. ALL my tabs get an extra ‘x’. Not
The reported issue will be resolved with next release of our Tabs widget. Thank you for the valuable feedback!
Thanks Peter. It would be great if you could get this into a 4.5.x fix release. I’m doing demos of an app to both developers and potential clients and it really diminishes from the quality of the interface. Thanks for anything you can do.
Hi JQWidgets Team,
I know you have your hands full but I am still waiting for a fix or advice or a workaround for the same tab title problem that I reported in November of 2016. My app uses dynamic tabs prominently and becomes unusable once 7 or 8 or 9 tab close x’s appear on every tab. All my non-selected tabs receive an additional ‘x’ whenever I address the selected tab with a setTitleAt.
Can you please advise:
1. Whether you’ve confirmed this is a problem – maybe my code structure is contributing to the problem somehow?
2. Is there a workaround?
3. Is there a simple demo I can run myself to confirm the problem and perhaps hunt for a workaround?
4. Approximately when this fix will be released? I may have to consider a significant restructuring of my UI without dynamic tabs.
Thanks for your advice,
You must be logged in to reply to this topic.