Recommended Posts

-moz-element support landed in tonight's nightly, it allows you to use another element in the document as an image source (e.g. a slide show presentation can show real time updating thumbnails of the slides)

It's mainly going to be used in the OS X theme for rendering Persona's, but web content can also use it (WebKit has supported something similar for a few years now, but much more limited)

-moz-element support landed in tonight's nightly, it allows you to use another element in the document as an image source (e.g. a slide show presentation can show real time updating thumbnails of the slides)

It's mainly going to be used in the OS X theme for rendering Persona's, but web content can also use it (WebKit has supported something similar for a few years now, but much more limited)

Sounds interesting. Do you know the syntax? Google has little info on it.

<img id="img" src="blah.png" width="128" height="128">
<div style="width: 128px; height: 128px; background-image: -moz-element(#img);"> </div>

Simple (and stupid) example, but that's basically how you use it (it updates at the same time as the source element draws, so <video> and <canvas> is still fast, etc.)

Edit: That + SVG Filters is what the OS X theme will use, a filter to darken the persona image behind the tab bar, and possibly a Aero Glass like blur for behind the toolbar buttons.

Get ready to see about 50~100ms (depending on system) boost in SunSpider tests with today's nightly! (If curious , check the hourlies)

sweet, there wasn't much improvement in beta3, was hoping firefox would close the large gap with the other browser vendors. Will benchmark beta 4:)

&lt;img id="img" src="blah.png" width="128" height="128"&gt;
&lt;div style="width: 128px; height: 128px; background-image: -moz-element(#img);"&gt; &lt;/div&gt;

Simple (and stupid) example, but that's basically how you use it (it updates at the same time as the source element draws, so <video> and <canvas> is still fast, etc.)

Edit: That + SVG Filters is what the OS X theme will use, a filter to darken the persona image behind the tab bar, and possibly a Aero Glass like blur for behind the toolbar buttons.

Very cool, thanks for the info. Seems really useful because it uses a live preview of that element.

It is pretty cool, it can really slow down the browser though if you do it incorrectly (Like pointing it at the <html> element as the source, it uses 100% of the CPU core then)

Also, D2D bounced (i.e. it landed, but was backed out), so it's disabled by default again (but not in the current nightly)

I tried a nightly out with the same result, but anyone know why Firefox and Flash don't seem to be getting on in the Beta 3?

And when clicking the fast reply box does it not work till you click a second time for anyone else?

I have issues with flash too, when I play a video and scroll up or down, I can't acces the seekbar and other buttons until I scroll to the initial position (all betas).

I have issues with flash too, when I play a video and scroll up or down, I can't acces the seekbar and other buttons until I scroll to the initial position (all betas).

Directwrite is still significantly delaying startup of firefox even in the latest nightly (I open firefox and everything in the window is white for like 30 secs and its unresponsive)

I am also having these issues.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!