Smart GWT - button problem with chrome - gwt

i've a problem with smart-GWT and google Chrome. I don't see the IButton and the ButtonItem as well as Internet Explorer or Forefox 4.
This problem happen when i use an HTML code created with Dreamweaver, that use Table.
Can you help me?

I would suggest not using the Table element. CSS with divs are easier to use in the long run.
Having said that, I have found some funny behaviour using the SmartGWT IButton and IE 9.0, I have to render the page in compatibility mode or else the button doesn't work. It works fine in Chrome, but SmartGWT 2.4 was released in Dec 2010, so maybe an update is due out soon that will address this.

Related

TinyMCE 4 Issues on IE 11

I have recently updated some admin systems on websites to use TinyMCE 4, using the JS version.
I have just discovered a bug that only occurs in IE11, which is the following:
When a Textarea loads it contains the posted html data, but then after the split second it takes for TinyMCE to trigger, all the content within the Textarea is hidden - and TinyMCE is just empty.
It seems to work on all other browsers, including other versions of Internet Explorer. Has anyone else had this issue and know of a solution?
Cheers
We've fixed this bug since then. Updating to the latest version should fix this.

Kendo Ui DatePicker Cannot Select Date in IE

Has anyone had problems with Kendo DatePicker in IE9 Compatibility Mode? I am not able to select a date from the calendar except for the current date at the bottom. I found this post, jQuery UI datepicker IE problem, but it did not offer any clues to the problem. This post, http://www.kendoui.com/forums/ui/date-time-pickers/datepicker-use-ie9-compatibility-mode-ie7-or-ie8-day-not-selected.aspx, also addresses the issue, but the issue still remains. I am currently running Kendo UI Web 2013.1.319 Open Source. Per usual everything is working exactly as expected in Firefox, Chrome, and other modern browsers. Thank you for any help offered.

fancybox iframe not working with Mozilla and Chrome

I am using a fancybox version 1.3.4 to open another page in iframe. It is working fine in IE but not in Mozilla or Chrome. It is just opening another page without creating any overlay. Is the compatibility issue ? How can I fix this ?
I've no answer but I stumbled on a-not-working-fancybox.. To JFK: and concerning an url: going back to base is more then often a good starting point :) so at the fancybox-homepage the iframe-example is not fully functional and more: I've downloaded the fancybox plugin and also there de iframe link (and ajax-example) is not really functional.. (btw I'm using FF7).. Greetings

joomla tinymce editor problem

hi i am using joomla 1.5 for my site.
in this i fetched the problem of tinymce editor when i clicked on any article the image button are not shown. when i clicked on edit html source button It showing only “{$lang_theme_code_title}” on the Title bar and all body is blank.
so plz help me to resolved out from this problem.
thanks in advance
You should consider trying the JCE editor instead of trying to debug Tinymce. I'm running JCE error free on over 40 sites. It has a superior image manager, link manager, and code view. It installs easily and is highly configurable. The only caveat is that you should disable the Joomla insert image, page break, and read more buttons as JCE has those built in.
http://extensions.joomla.org/extensions/edition/editors/88
See this thread:
http://forum.joomla.org/viewtopic.php?t=62545
Try adding www. to your domain. Most often this is the problem.
I searched joomla project for vars $lang_theme_code_title... and related... There are not. Looked at Tinymce editor, it has javascript driven language file...
Most likely problem is cause by JavaScript. Try using different browser (firefox or chrome).
I read info on some other forums, some claim that temporarily disabling the antivirus solved the problem. I don't think that this will work, but you can try.
If none of this helps, you will need to give more information. Load firefox with firebug and see the NET tab for JavaScript files and Ajax Requests, most likely you'll find something interesting there (i think 500 Error)

GWT History and IE6 / 7

I've asked this question on the GWT group with no luck, so now I'm trying Stack Overflow :)
There seems to be some problem with GWT's history and IE6 / 7, and I'm trying to confirm this is an actual problem with GWT and not just something stupid I've done.
The problem I run into is the following:
Imagine you have some GWT app that plugs in to your existing website. It has internal history and works fine. Let's just say it's a tree. What it is isn't important, just that it has state that you can go back and forwards in. Part of this app is links to other parts of your website. Click one of those and you exit the GWT application.
Now, use the "back" button after you've clicked one of these links. You return to the GWT application which loads fine and the state is recreated using whatever is in the URL.
If you the click back again, here's where I get differing results in IE6 / 7 and FF / Chrome / IE8. In IE6 / 7 this second "back" sends me to the page before the GWT app. In FF / Chrome / IE8 this second back sends me back in the state of the GWT app, which is what I want, naturally.
I've checked my code, and as far as I can see, this second "back" just goes directly to the page before. My history handler is never called, at any rate.
Has anyone else run into this? Or know of anywhere this problem is discussed? I've googled extensively with no results.
The GWT group is to noisy to get confirmations of potential bugs, it's mostly for beginners.
The approach I take when I start to assume that there is a bug in GWT, and after trying to get help from the GWT group, is to create an issue in the GWT issue tracker and cross posting in the GWT contributors group as well.
Here is the URL for creating an issue:
http://code.google.com/p/google-web-toolkit/issues/list
Make sure that you first search the issue list for possible duplicates.
I've not yet played with history in GWT since our apps are running in an IFrame and that just kills the possibility to implement history.