Updates:
Labels: -Mstone-4 Mstone-X
Comment #26 on issue 3765 by js...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
(No comment was entered for this change.)
--
You rece
Comment #25 on issue 3765 by prog...@chromium.org: Encoding menu is
disabled when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
update: the Enocoding menu is no longer grayed-out with the current versions
BUT since the page
Updates:
Labels: -mstone-3 Mstone-4
Comment #24 on issue 3765 by lafo...@chromium.org: Encoding menu is
disabled when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
(No comment was entered for this change.)
--
You re
Comment #21 on issue 3765 by progame: Encoding menu is disabled when
about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
btw, isn't the real issue the fact that the window is still identified as
about:blank
after it is redirecte
Updates:
Labels: -Mstone-2.0 Mstone-2.1
Comment #20 on issue 3765 by js...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
Because haaretz.co.il is not affected by this any
Updates:
Status: Assigned
Owner: js...@chromium.org
Cc: -js...@chromium.org
Comment #19 on issue 3765 by js...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
Comment #17 on issue 3765 by progame: Encoding menu is disabled when
about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
another example:
Haaretz website's new comment form now has the same problem
and since Haaretz website's new
Comment #18 on issue 3765 by progame: Encoding menu is disabled when
about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
another example:
Haaretz website's new comment form now has the same problem
and since Haaretz website's new
Updates:
Status: Available
Owner: ---
Cc: js...@chromium.org
Labels: -stable -Pri-1 Pri-2
Comment #16 on issue 3765 by m...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/
Updates:
Status: Assigned
Cc: anan...@chromium.org
Comment #13 on issue 3765 by xly...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
Fixed for Jon's sample, but th
Comment #12 on issue 3765 by progame: Encoding menu is disabled when
about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
my PC is dead so i can't test it myself
Is it also fixed for the url mentioned in the reproduction steps for
Updates:
Status: Fixed
Comment #11 on issue 3765 by j...@chromium.org: Encoding menu is disabled
when about:blank is replaced by an html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
I created this sample that should demonstrate the problem:
Issue 3
Issue 3765: Encoding menu is disabled when about:blank is replaced by an
html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
Comment #9 by progame:
interesting, thanks for updating :)
--
You received this message because you are listed in the owner
or CC fi
Issue 3765: Encoding menu is disabled when about:blank is replaced by an
html document (in javascript)
http://code.google.com/p/chromium/issues/detail?id=3765
Comment #8 by [EMAIL PROTECTED]:
This bug turned out to be much less serious than I thought initially. Usual
pop-ups
opened with 'wind
14 matches
Mail list logo
