iFrame problem with Chrome 10

[justaguy]

The intention of the following code to for text entry and/or WYSIWYG
editing:

<iframe id="txt" designMode="on" editable="true" src="blabla.html" />

Status:
It works with IE7/8/9, Firefox 3.x and Safari 5 but with Chrome 10,
the iframe simply freezes. How can we solve this problem.

Thanks in advance.

[Scott Fujan]

This group is for Chrome Extensions, not general web programming.

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

[Zachary “Gamer_Z.” Yaro]

I have had issues with editable iframes in Chrome 11 and 12 as well, even though the editor works fine in other browsers.  Does Chrome just not like editable iframes?

--Zachary “Gamer_Z.” Yaro

[Zachary “Gamer_Z.” Yaro]

I am aware of that, which is why I never asked about it here.  But since someone brought it up and this is a mailing list with many Chrome developers, it would be useful to know if someone knows a solution.

--Zachary “Gamer_Z.” Yaro

[Arne Roomann-Kurrik]

Anything which freezes the UI is a bug.  Please follow the steps listed here to report it: http://code.google.com/chrome/extensions/faq.html#faq-fea-01

~Arne

[Don Li]

I thought I've entered the bug but did a query for it, couldn't find it any more, not sure what's going on here...

[Arne Roomann-Kurrik]

I can't seem to find it either.  Try opening a new bug and sending the URL to this list.

~Arne

[Don Li]

Thanks for your kind note, however, I'm not confident that it won't be removed again.

[PhistucK]

No bugs are removed.

It might have just been lost in the search, the search engine sometimes does not yield all of the results.

Please, create a new issue.

☆PhistucK

[Don Li]

Too bad.

Firefox (3.6.17) or something else is not cooperating.  At the bug reporting site, 
URL,
http://code.google.com/p/chromium/issues/entry?template=Defect on Windows&comment=Chrome...

I entered the following to in the form, the Submit button isn't disabled, however, clicking on it won't submit the form.  Then, I attempted with Safari 5, with the same outcome.  Maybe my computer has been hacked something.   Could any of you kindly posted it for me instead?


Chrome Version       : 12.0.742.91
OS Version: 6.1 (Windows 7)
URLs (if applicable) : NA
Other browsers tested: see below

What steps will reproduce the problem?
Objective:
Load the blabla.html into the iframe with id of "myFRM" and make the text editable.

Code:
<iframe id="myFRM" designMode="on" contentEditable="true" src="blabla.html"></iframe>

Status:
It works fine with IE 7/8/9 and Firefox 3.6 and Safari 5 on Windows 7
and Chrome 5 on XP, however, it fails with Chrome 10/11/12 on Windows 7.

Any idea?

Thanks in advance.

What is the expected result?
Load the blabla.html into the iframe with id of "myFRM" and make the text editable.


What happens instead?
iframe shows up, however, no cursor movement inside.

Please try it.

[Don Li]

Sorry, never mind, upon another try, it posted.

[Arne Roomann-Kurrik]

Do you have the URL to the bug?

~Arne

[Don Li]

Yes,

http://code.google.com/p/chromium/issues/list?can=2&q=iframe&sort=-modified&colspec=ID%20Stars%20Pri%20Area%20Feature%20Type%20Status%20Summary%20Modified%20Owner%20Mstone%20OS

id of 85501

Thanks.

[Scott Fujan]

A good way of linking to bugs is: crbug.com/85501

[Don Li]

all right, are you guys going to fix it soon?  i also noticed that there's others posting similar issue as well...

[Arne Roomann-Kurrik]

1: This is a general problem with chrome and has nothing to do with extensions

2: You should follow progress of the issue on the bug itself - not on this thread

3: I'm not sure that this is a bug at all.  As far as I can tell, this isn't a specified behavior anywhere (just an IE only thing).  Please follow up on the bug if there's some sort of specification you can link to which explains the expected behavior.

~Arne