[MASTER] checking radio buttons or checkboxes doesn't work correctly

Bug #220575 reported by ANDREA
86
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned
firefox-3.0 (Ubuntu)
Invalid
Undecided
Unassigned
gtk-qt-engine (Ubuntu)
Won't Fix
Medium
Unassigned
gtk-qt-engine-kde4 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

when selecting a check box or radio button, they show up as "active" but not as checked. I've made a quick video to illustrate what I mean. this is a real pain in the end of the back because when you quickly "eye-check" if you've accepted the terms and conditions (checkbox!) or so you're gonna clear that one by accident etc.

sorry the video was made with pyvnc2swf so it's an swf object. if someone has problems viewing it create a html file with the following in it: {gonna be long...}

<script language="javascript">
/* Jesse Ruderman
 * July 18, 2004
 *
 * Remaining problems:
 * IE sometimes crashes on exit after using the this script.
 * In IE, it is a little ugly because IE doesn't support border-radius.
 * In IE, it does not work at standalone Flash URLs.
 */

function setupSeekBar() {

setTimeout(initFlashControls, 100);

function initFlashControls()
{
  var count = 0;

  function tt(elem)
  {
    if (typeof elem.TotalFrames != "undefined") /* do not coerce elem.StopPlay to bool, because that breaks IE */
    {
      addFlashControls(elem);
      ++count;
    }
  }

  var i, x;

  for (i = 0; x = document.getElementsByTagName("object")[i]; ++i)
    tt(x);

  for (i = 0; x = document.getElementsByTagName("embed")[i]; ++i)
    tt(x);

}

function addFlashControls(flash)
{
  var controlsDiv = document.createElement("div");

  /* Put the controls under the Flash.
   *
   * If the Flash is an <embed> in an <object>, we do not want to touch the <object>, because that would make
   * Mozilla re-test whether the <object> is broken and reset the <embed>. So in that case, we put the controls
   * under the <object>.
   */
  var where = flash;
  while (where.parentNode.tagName.toLowerCase() == "object")
    where = where.parentNode;
  where.parentNode.insertBefore(controlsDiv, where.nextSibling);

  /* Construct controls using DOM2 instead of innerHTML.
   * In Mozilla, innerHTML= is like innerText= at standalone flash URLs.
   */
  var table = document.createElement("table");
  controlsDiv.appendChild(table);

  var row = table.insertRow(-1);

  var pauseButton = document.createElement("button");
  pauseButton.appendChild(document.createTextNode("Pause"));
  var buttonCell = row.insertCell(-1);
  buttonCell.appendChild(pauseButton);

  var slider = row.insertCell(-1);
  slider.width = "100%";

  var visibleSlider = document.createElement("div");
  visibleSlider.style.position = "relative";
  visibleSlider.style.height = "10px";
  visibleSlider.style.width = "100%";
  visibleSlider.style.MozBorderRadius = "4px";
  visibleSlider.style.background = "#aaa";
  slider.appendChild(visibleSlider);

  var thumb = document.createElement("div");
  thumb.style.position = "absolute";
  thumb.style.height = "20px";
  thumb.style.width = "10px";
  thumb.style.top = "-5px";
  thumb.style.MozBorderRadius = "4px";
  thumb.style.background = "#666";
  visibleSlider.appendChild(thumb);

  var sliderWidth;
  var paused = false;
  var dragging = false;

  table.width = Math.max(parseInt(flash.width) || 0, 400);

  addEvent(pauseButton, "click", pauseUnpause);
  addEvent(slider, "mousedown", drag);
  addEvent(slider, "drag", function() { return false; }); /* For IE */
  window.setInterval(update, 30);

  function pauseUnpause()
  {
    paused = !paused;

    pauseButton.style.borderStyle = paused ? "inset" : "";

    if (paused)
      flash.StopPlay();
    else
      flash.Play();
  }

  function update()
  {
    sliderWidth = parseInt(getWidth(slider) - getWidth(thumb));

    if (!paused && !dragging)
      thumb.style.left = parseInt(flash.CurrentFrame() / totalFrames() * sliderWidth) + "px";
  }

  function dragMousemove(e)
  {
    var pageX = e.clientX + document.body.scrollLeft; /* cross-browser, unlike e.pageX, which IE does not support */
    var pos = bounds(0, pageX - getX(slider) - 5, sliderWidth);
    var frame = bounds(1, Math.ceil(totalFrames() * pos / sliderWidth), totalFrames() - 2);

    thumb.style.left = pos + "px";

    flash.GotoFrame(frame);
  }

  function release(e)
  {
    removeEvent(document, "mousemove", dragMousemove);
    removeEvent(document, "mouseup", release);
    if (!paused)
      flash.Play();
    dragging = false;
  }

  function drag(e)
  {
    addEvent(document, "mousemove", dragMousemove);
    addEvent(document, "mouseup", release);
    dragging = true;
    dragMousemove(e);
  }

  /* Boring functions, some of which only exist to hide differences between IE and Mozilla. */

  function bounds(min, val, max)
  {
    return Math.min(Math.max(min, val), max);
  }

  function totalFrames()
  {
    /* This is weird. TotalFrames differs between IE and Mozilla. CurrentFrame does not. */

    if (typeof flash.TotalFrames == "number")
      return flash.TotalFrames; /* IE */
    else if (typeof flash.TotalFrames == "function")
      return flash.TotalFrames(); /* Mozilla */
    else
      return 1; /* Partially loaded Flash in IE? */
  }

  function getWidth(elem)
  {
    if (document.defaultView && document.defaultView.getComputedStyle)
      return parseFloat(document.defaultView.getComputedStyle(elem,null).getPropertyValue("width")); /* Mozilla */
    else
      return parseFloat(elem.offsetWidth); /* IE (currentStyle.width can be "auto" or "100%") */
  }

  function getX(elem)
  {
    if (!elem) return 0;
    return (elem.offsetLeft) + getX(elem.offsetParent);
  }

  function addEvent(elem, eventName, fun)
  {
    if (elem.addEventListener) /* Mozilla */
      elem.addEventListener(eventName, fun, false);
    else /* IE */
      elem.attachEvent("on" + eventName, fun);
  }

  function removeEvent(elem, eventName, fun)
  {
    if (elem.addEventListener)
      elem.removeEventListener(eventName, fun, false);
    else
      elem.detachEvent("on" + eventName, fun);
  }

}

}
</script>
</head>
<body onload="setupSeekBar();">
<h1>clickingaction</h1>
<hr noshade><center>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="1280" height="800"
 codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0">
 <param name="movie" value="clickingaction.swf">
 <param name="play" value="true">
 <param name="loop" value="True">
 <param name="quality" value="low">
<embed src="clickingaction.swf" width="1280" height="800" play="true"
 loop="True" quality="low" type="application/x-shockwave-flash"
 pluginspage="http://www.macromedia.com/go/getflashplayer">
</embed></object></center>

Revision history for this message
ANDREA (andrea54) wrote :
Revision history for this message
ANDREA (andrea54) wrote :

this has been confirmed on several other computers running kubuntu 8.04 (fresh installs as well as upgrades). even when booting from the live cd and running firefox the check boxes, radio buttons etc. show this behavior.

there is one upgraded computer to my knowledge that does not show this behavior. i still haven't figured out what might be causing it though i've noticed that other gtk applications (firestarter) seem to "hang" a bit when first started after booting. has anybody else observed this?

Revision history for this message
John Vivirito (gnomefreak) wrote : Re: [Bug 220575] Re: checking radio buttons or checkboxes doesn't work correctly

ANDREA wrote:
> this has been confirmed on several other computers running kubuntu 8.04
> (fresh installs as well as upgrades). even when booting from the live cd
> and running firefox the check boxes, radio buttons etc. show this
> behavior.
>
> there is one upgraded computer to my knowledge that does not show this
> behavior. i still haven't figured out what might be causing it though
> i've noticed that other gtk applications (firestarter) seem to "hang" a
> bit when first started after booting. has anybody else observed this?
>
>
Please make sure you have firefox-gnome-support installed if not please
install it an dconfirm that it changes after restarting firefox

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 220575] Re: checking radio buttons or checkboxes doesn't work correctly

On Fri, May 09, 2008 at 09:37:19AM -0000, John Vivirito wrote:
> ANDREA wrote:
> > this has been confirmed on several other computers running kubuntu 8.04
> > (fresh installs as well as upgrades). even when booting from the live cd
> > and running firefox the check boxes, radio buttons etc. show this
> > behavior.
> >
> > there is one upgraded computer to my knowledge that does not show this
> > behavior. i still haven't figured out what might be causing it though
> > i've noticed that other gtk applications (firestarter) seem to "hang" a
> > bit when first started after booting. has anybody else observed this?
> >
> >
> Please make sure you have firefox-gnome-support installed if not please
> install it an dconfirm that it changes after restarting firefox
>

 status incomplete

 - Alexander

Changed in firefox:
status: New → Incomplete
Revision history for this message
ANDREA (andrea54) wrote : Re: checking radio buttons or checkboxes doesn't work correctly

Thank you for checking out this bug report, Alexander. Your comment/contribution itself however is rather incomplete or would you care to elaborate what about this bug report is incomplete? otherwise I have to say that your comment is really pointless.

thank you for closer instructions in advance and most importantly for your time!

ANDREA

ps: when you watch the screencast you'll see the problem. it's not an isolated case by the way; when running from the live cd, install firefox (sudo apt-get install firefox) and well navigate the web and you'll see that all checkboxes are kind of .... "screwed up".

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 220575] Re: checking radio buttons or checkboxes doesn't work correctly

On Tue, May 13, 2008 at 12:00:07PM -0000, ANDREA wrote:
> Thank you for checking out this bug report, Alexander. Your
> comment/contribution itself however is rather incomplete or would you
> care to elaborate what about this bug report is incomplete? otherwise I
> have to say that your comment is really pointless.
>
> thank you for closer instructions in advance and most importantly for
> your time!
>
> ANDREA
>
> ps: when you watch the screencast you'll see the problem. it's not an
> isolated case by the way; when running from the live cd, install firefox
> (sudo apt-get install firefox) and well navigate the web and you'll see
> that all checkboxes are kind of .... "screwed up".
>

please see if changing the gnome theme/engine changes a thing ...

 status incomplete

 - Alexander

Revision history for this message
ANDREA (andrea54) wrote : Re: checking radio buttons or checkboxes doesn't work correctly

hi alexander
thanks for your reply. I have indeed tried different gnome themes. i did not get what you mean by " engine change" though. in kcontrol (using kubuntu 8.04 with kde 3.5.9) i went to gtk styles and switched thru them. still no better...

i appreciate your help on this :-)

ANDREA

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 220575] Re: checking radio buttons or checkboxes doesn't work correctly

On Tue, May 13, 2008 at 02:08:41PM -0000, ANDREA wrote:
> hi alexander
> thanks for your reply. I have indeed tried different gnome themes. i did not get what you mean by " engine change" though. in kcontrol (using kubuntu 8.04 with kde 3.5.9) i went to gtk styles and switched thru them. still no better...
>
> i appreciate your help on this :-)
>

For now i assume that this is a gtk-qt-engine bug

 affects ubuntu/gtk-qt-engine
 status new

maybe its even gone in kde4? Someone should try to reproduce this in kde4

 affects ubuntu/gtk-qt-engine-kde4
 status incomplete

but its not a firefox bug as i don't see it using the default ubuntu
engine

 affects ubuntu/firefox-3.0
 status invalid
 affects ubuntu/firefox
 status invalid

 - Alexander

Changed in firefox:
status: Incomplete → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote : Re: checking radio buttons or checkboxes doesn't work correctly

Does not effect gtk-kde-engine-kde4, though when I was using Gutsy I did see this problem with gtk-qt-engine.

Changed in gtk-qt-engine-kde4:
status: Incomplete → Invalid
Changed in gtk-qt-engine:
status: New → Confirmed
Revision history for this message
ANDREA (andrea54) wrote :

this bug is actually worse than i thought. programs using gtk won't really load until like 5 min later. today evince wouldn't load at all, and firestarter usually takes a long time. i've abandoned firefox for now (using opera) but on another computer it's still loading really slowly. any solutions?

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 220575] Re: checking radio buttons or checkboxes doesn't work correctly

On Sat, May 17, 2008 at 09:24:06AM -0000, ANDREA wrote:
> this bug is actually worse than i thought. programs using gtk won't
> really load until like 5 min later. today evince wouldn't load at all,
> and firestarter usually takes a long time. i've abandoned firefox for
> now (using opera) but on another computer it's still loading really
> slowly. any solutions?
>

This performance issue is not covered in this bug. Could you please
open a new bug using the ffox Help -> Report A Problem menu entry?
(Note: you need ubufox installed to get that menu entry)

Maybe test if this is related to some extension by disabling them
before filing a new bug

Thanks,

 - Alexander

Revision history for this message
jetpeach (jetster) wrote : Re: checking radio buttons or checkboxes doesn't work correctly

i too have this bug, on all 4 of my kubuntu 8.04 machines. it still exists with Firefox RC1 as of 6/12

does anybody have a workaround or fix?

Revision history for this message
jetpeach (jetster) wrote :

bug https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/194624 is a dup of this, but has much good information and a fix- here is the process (for KDE3):

install the package gtk2-engines-qtcurve
go to to system settings, Appearance/GTK Styles and Fonts, then select "use another style" and choose Qtcurve.

before the fix worked, i had to restart KDE and firefox

Miklós Juhász who helped with the fix in the other bug had a bit more info on the fix, i'll copy and pasted below for simplicity
"
This eliminates the firefox rendering bug and many other issues like sliders are chopped off at the bottom, etc.

As far as I understand the problem is that Hardy uses QtCurve as the default KDE theme. However Hardy does not use QtCurve's Gtk2 engine, preferring to style Gtk2 apps via the Qt engine. QtCurve doesn't look that great when done this way - certainly nowhere near as good as its native Gtk2 port.

For more information, see this thread on Kubuntu-devel list:
https://lists.ubuntu.com/archives/kubuntu-devel/2008-March/002239.html
"

Revision history for this message
Alexander Sack (asac) wrote :

not really a blocker issuze, but for the engine itself this is Medium imo.

Changed in gtk-qt-engine:
importance: Undecided → Medium
Revision history for this message
ANDREA (andrea54) wrote :

by the way the performance issue part is documented here:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/231384
as an independent bug just in case somebody else is experiencing similar problems.

the qt-curve idea does work, seems suboptimal though ... maybe kubuntu-desktop (or other package) should change dependency or something? it really shouldn't be that everybody has to manually change this stuff :-)

Revision history for this message
JDS (jsilveronnelly) wrote :

I have this bug. Here is a workaround!

Using KDE 3.5 on Ubuntu 8.04

The workaround is simple: Choose "Use another style" in the GTK Styles and Fonts dialog.

In KDE, this would be here:

K-Menu->Settings->Control Center->Appearance & themes->GTK Styles and Fonts->GTK Styles (the first box in the dialog)

Selecting "Use my KDE style in GTK Applications" will trigger the bug in FF3. But NOT, as near as I can tell, in other GTK apps.

This is only a workaround! And, as always, thank you, the developers, for the great Ubuntu product(s).

Revision history for this message
mike hancock (javaiscoolmike) wrote :

after doing what JDS said, it did not work for me; and i reopend the control center and noticed that the setting did not 'save' after i selected the second option. i tryed again, but the setting would not stick

Revision history for this message
zexpe (rosscollins-uk) wrote :

Mike, the workaround would only work for me if I chose the QtCurve style. Follow jetpeach's intructions above. Looking at what he says, I suggest you need the QtCurve style for both KDE and the GTK applications too. I'm now using QtCurve for both without problems.

Revision history for this message
Gonzalo Servat (gservat) wrote :

Hi, I'm using Kubuntu as well and I had the same problem in KDE3. I decided to switch to Gnome (due to other reasons) so I installed the ubuntu-desktop dummy package. Anyway, I'm having the exact same problem in Gnome.
In Firefox/Epiphany, when I click on a checkbox, a dotted box appears around the checkbox and the contents are white so the box appears as if it wasn't ticked, even though it is. If I click outside the box, the checked-checkbox appears. With multiple select boxes, any selected items are not displayed as such until focus is given to the select box. Radio buttons also exhibit the same behavior as checkboxes. Strange thing is in Konqueror and Opera, it works fine. Only Firefox/Epiphany (and others, perhaps?) are affected so whatever engine they use to render these elements is evidently the problem.

I've tried the suggestion mentioned in this bug report of installing gtk2-engines-qtcurve. I selected it as my "Control" theme in GNOME. Restarted Gnome + Firefox and same result.

The closest I've come to fixing it is using some really weird theme in System -> Preferences -> Appearance at which point checkboxes started working OK, same as radio buttons, but I've not been able to fix the multiple select options bit.

I'd appreciate any suggestions on this!

Thank you.

Revision history for this message
Gonzalo Servat (gservat) wrote :

So far, it looks like anyone using Firefox 3.x and Kubuntu are having this issue. I just went to another PC running KDE and it had this problem too. Most people are just "used to it" but I simply can't so I want to find a fix. It's certainly fixable for KDE as per the instructions in https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/194624 (installing gtk2-engines-qtcurve and selecting the QtCurve theme) but for users of Gnome in Kubuntu (like myself) it doesn't fix it. Yes, I know I probably shouldn't be using Gnome if my distribution is Kubuntu but I decided to make the switch and changing distributions at this time would require too much time. Besides, I'm not sure if this problem is specific to Kubuntu or not.

So, if anyone has a solution for Gnome, I'd (and many other people) would appreciate it!

Revision history for this message
Ryan Novosielski (novosirj) wrote : Re: [Bug 220575] Re: [MASTER] checking radio buttons or checkboxes doesn't work correctly

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gonzalo Servat wrote:
> So far, it looks like anyone using Firefox 3.x and Kubuntu are having
> this issue. I just went to another PC running KDE and it had this
> problem too. Most people are just "used to it" but I simply can't so I
> want to find a fix. It's certainly fixable for KDE as per the
> instructions in
> https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/194624
> (installing gtk2-engines-qtcurve and selecting the QtCurve theme) but
> for users of Gnome in Kubuntu (like myself) it doesn't fix it. Yes, I
> know I probably shouldn't be using Gnome if my distribution is Kubuntu
> but I decided to make the switch and changing distributions at this time
> would require too much time. Besides, I'm not sure if this problem is
> specific to Kubuntu or not.
>
> So, if anyone has a solution for Gnome, I'd (and many other people)
> would appreciate it!

I think you are confused here. Kubuntu is simply Ubuntu with
kubuntu-desktop installed. Ubuntu is simply Ubuntu with ubuntu-desktop
installed, etc. There is no distinction that I'm aware of otherwise
(possibly aside from the splash screen if you don't take extra steps to
change it).

- --
 ---- _ _ _ _ ___ _ _ _
 |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
 |$&| |__| | | |__/ | \| _| |<email address hidden> - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI7MDfmb+gadEcsb4RAhZcAJ98n26LXH+DiPnbF+AnUAohb+LcmwCfSLiM
U4JWmfz2CT9QdXO6up2ylhY=
=FQgL
-----END PGP SIGNATURE-----

Revision history for this message
Gonzalo Servat (gservat) wrote :

Hi Ryan,

Yes, sorry, I didn't know if there were other changes made when creating the Kubuntu distribution.

Anyway, the good news is that I managed to fix it. Changing the GTK2 theme in KDE will only change it when using KDE, so I had to find a way to do it for Gnome. I simply created ~/.gtkrc-2.0 with the following:

include "/usr/share/themes/Clearlooks/gtk-2.0/gtkrc"

I could have used QtCurve, but the highlighting color when selecting options in a multiple select list on LCD screens makes it hard to see sometimes so I switched to Clearlooks.

Revision history for this message
Jel Coward (jel-wildmedic) wrote :

I get the overly shadowed/malaligned check boxes when printing in Firefox 3 from Windows (all seems well in my ubuntu 8.04)

Revision history for this message
Mike D (sonofafool-deactivatedaccount) wrote :

I experienced this issue as well. I wanted to add that installing the package gtk2-engines-qtcurve did not resolve the issue (in fact it was already installed when the issue started).

I had to go to the Clearlooks theme in order to fix this.

Revision history for this message
jacob.lcl (jacob-lcl) wrote :

Bump.

I have the same checkbox issue with Kubuntu 8.04.1. It is very annoying.

pomodoro (zanyuan)
Changed in firefox-3.0:
status: Invalid → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

not a firefox issue; fix the engine.

Changed in firefox-3.0 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Sadly, gtk-qt-engine is a quite broken piece of software and has been removed from distribution. (See bug 404930)
Unfortunately this means that the large number of bugs will not be seeing fixes. :(

For now, the best integration option for KDE is the QtCurve style, (gtk2-engines-qtcurve) which offers a theme quite similar to the default Oxygen theme. The configuration module for gtk-qt-engine has been salvaged and is now living in the kcm-gtk package, which will be available and installed by default in Kubuntu 9.10.

Thanks for understanding. This package tried its best, but in the end did not live up to the standards required by anybody who doesn't like looking at a broken Oxygen imitation.

Changed in gtk-qt-engine (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
pomodoro (zanyuan) wrote : Re: [Bug 220575] Re: [MASTER] checking radio buttons or checkboxes doesn't work correctly
Download full text (8.1 KiB)

Thanks for detailed explanation though I don't quite understand those
programming terms.
I'll live up to it and look forward to the future...hopefully.

Stephen

On Thu, Jul 30, 2009 at 6:33 AM, Jonathan Thomas <email address hidden>wrote:

> Sadly, gtk-qt-engine is a quite broken piece of software and has been
> removed from distribution. (See bug 404930)
> Unfortunately this means that the large number of bugs will not be seeing
> fixes. :(
>
> For now, the best integration option for KDE is the QtCurve style, (gtk2
> -engines-qtcurve) which offers a theme quite similar to the default
> Oxygen theme. The configuration module for gtk-qt-engine has been
> salvaged and is now living in the kcm-gtk package, which will be
> available and installed by default in Kubuntu 9.10.
>
> Thanks for understanding. This package tried its best, but in the end
> did not live up to the standards required by anybody who doesn't like
> looking at a broken Oxygen imitation.
>
> ** Changed in: gtk-qt-engine (Ubuntu)
> Status: Confirmed => Won't Fix
>
> --
> [MASTER] checking radio buttons or checkboxes doesn't work correctly
> https://bugs.launchpad.net/bugs/220575
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “firefox” package in Ubuntu: Invalid
> Status in “firefox-3.0” package in Ubuntu: Invalid
> Status in “gtk-qt-engine” package in Ubuntu: Won't Fix
> Status in “gtk-qt-engine-kde4” package in Ubuntu: Invalid
>
> Bug description:
> when selecting a check box or radio button, they show up as "active" but
> not as checked. I've made a quick video to illustrate what I mean. this is a
> real pain in the end of the back because when you quickly "eye-check" if
> you've accepted the terms and conditions (checkbox!) or so you're gonna
> clear that one by accident etc.
>
> sorry the video was made with pyvnc2swf so it's an swf object. if someone
> has problems viewing it create a html file with the following in it: {gonna
> be long...}
>
> <script language="javascript">
> /* Jesse Ruderman
> * July 18, 2004
> *
> * Remaining problems:
> * IE sometimes crashes on exit after using the this script.
> * In IE, it is a little ugly because IE doesn't support border-radius.
> * In IE, it does not work at standalone Flash URLs.
> */
>
> function setupSeekBar() {
>
> setTimeout(initFlashControls, 100);
>
> function initFlashControls()
> {
> var count = 0;
>
> function tt(elem)
> {
> if (typeof elem.TotalFrames != "undefined") /* do not coerce
> elem.StopPlay to bool, because that breaks IE */
> {
> addFlashControls(elem);
> ++count;
> }
> }
>
> var i, x;
>
> for (i = 0; x = document.getElementsByTagName("object")[i]; ++i)
> tt(x);
>
> for (i = 0; x = document.getElementsByTagName("embed")[i]; ++i)
> tt(x);
>
> }
>
>
> function addFlashControls(flash)
> {
> var controlsDiv = document.createElement("div");
>
> /* Put the controls under the Flash.
> *
> * If the Flash is an <embed> in an <object>, we do not want to touch the
> <object>, because that would make
> * Mozilla re-test whether the <object> is broken and reset the <embed>.
> So in that case, we put the co...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.