サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
ドラクエ3
blog.mozilla.com
Recently there have been a number of blog posts on optimizations possible via Local StorageAPI. When Microsoft, Google, Amazon and a number of others aggressively adopt a new feature, people notice. The optimization is to use Local Storage to reduce network requests and/or payload size. This should result in a more responsive experience for the user… except when it doesn’t. This strategy can backf
Another six months and we have our first release. Rust is now at a point where we’d like to invite people to write code in it. It’s not set in stone — things will change, code will break — but we’re comfortable expanding the set of users a little beyond the set of compiler hackers. You can write interesting programs and libraries in it now; we’d like to see adventurous people try to do so, and see
Release Management Blog Thoughts and facts on shipping quality software by the team that ships Firefox every 4 weeks We work hard as an organization to ship the best browser possible every 4 weeks with about 1000 new patches per release. We ship new features to make our browser useful and easy to use. We also do platform work to be able to render new sites and web applications while remaining comp
Two weeks ago I started project Snappy. The purpose of the meeting is to help us focus on eradicating jarring pauses in Firefox. Today we had our second meeting (notes). A surprising amount of work has happened between the first and second meeting: Chromehang was briefly turned on. This converted browser stalls of >30seconds into crashes. This showed that a number of issues are worse than previou
The latest Firefox release includes a new tool for web developers: Scratchpad. The idea behind Scratchpad is simple: the browser is a fantastic place to experiment with JavaScript. Most JavaScript developers already know this and they use tools like the Web Console or Firebug’s command line to take advantage of the one environment that knows everything about their web page. Tools like the Web Cons
In Firefox 4, we switched from using the GDI on Windows to using the DirectWrite API on platforms that support it such as Windows 7. This was required for supporting hardware acceleration via Direct2D but DirectWrite also is a more modern API without many of the quirks and foibles that the GDI API still has. DirectWrite is also used by IE9 while Chrome continues to use GDI. Initially, there were D
Last week, John J. Barton announced that he has left IBM and the Firebug project and joined Google. John has been leading Firebug for quite some time and he has made a huge contribution there. It’s hard to overstate how important Firebug has been and still is in the world of web development, and John has been a large part of that history. The departure of Firebug’s leader has raised questions in s
We will be making an update available to Firefox 5 before the scheduled release of Firefox 6. This update will affect Macintosh users only. This update will fix two specific problems: There is a bug present in the upcoming release of OSX 10.7 that causes Firefox to crash when using downloadable fonts. Downloadable fonts are used widely on the web, so users would have suffered severe crash probl
Last Friday, pdf.js reached the state we wanted to it to be in before announcing it loudly: it renders the Tracemonkey paper perfectly*. So, we’re announcing it! Try out version 0.2. We’re very excited about the progress since the cat was let out of the bag two weeks ago. Below is a comparison of some pages as rendered by the version of pdf.js initially covered by the press and our v0.2 release. I
Visualizing the DOM nodes depth and coordinates 06.13.11 - 09:01am The most important part of Tilt was actually visualizing the DOM nodes depth and coordinates in 3D manner, by positioning them relative to parent offsets and sizing them based on the client width and height dimensions. This is exactly what’s been implemented in the past week, so let’s take a look. This is an idea of the direction
Today I pushed a patch to our development repository to expose the JavaScript Parser API to code with chrome privileges. I’ve fixed all known major bugs, and it’s been holding up under sustained attack from Jesse Ruderman‘s fuzz tester without crashing for the better part of a year. So hopefully this means the landing will stick. If so, then this should land in Nightly within the week and Aurora b
Andreas posted a general overview of pdf.js. I’d like to briefly cover some more-technical parts of the renderer. pdf.js (currently) parses raw arrays of bytes into streams of PDF “bytecode”, compiles the bytecode into JavaScript programs, then executes the programs. (Yes, it’s a sort of PDF JIT . The side effect of those programs is to draw on an HTML5 <canvas>. The commands in the bytecode inclu
In my last post I introduced a few different reasons why we are exploring the concept of a Home Tab, including: -Creating an interface that is unique to Firefox in a browser market headed towards commoditization (back+ forward+fast!) -Ambient application-level notification -Introducing the concept of tab browsing to users of the home button -Building up the user’s mental model of the features t
Motivation Firefox 4′s graphics performance is great, and some last-minute “low-hanging fruit” inefficiencies Robert O’Callahan found made us even faster on some demos in Firefox 5. We’re not content with “great”, though, and our investigations into how to make drawing even faster have revealed that some of our choices in Gecko’s graphics engine aren’t optimal for performance. How Mozilla renders
So, JägerMonkey is done (as of last fall, really), and Firefox 4 is out (yay! and whew!), so that means we can get back to the fun stuff: new coding projects. At the Platform Work Week, we firmed up plans for JavaScript for the next year or so. The main themes are debugging and performance: New Debugging API. We are going to give the JS engine a new debugging API, called the Debug object. The new
The V8 team has dropped Crankshaft, a new JIT system for JavaScript, into their bleeding-edge repo. According to their blog entry, it doubles their speed on 3 of 8 V8 benchmarks, and improves page load time by 12% on JS-heavy pages. First off: Congratulations to the V8 team. It looks like great work, pushing forward what kinds of things JS can do in the browser. I look forward to checking out the
These two banner ads appeared on the Japanese version of Slashdot. The wording on the top one from last week includes “Google chrome, a browser built from scratch by Google” but the one this week just says “Google chrome, a browser built by Google”. Um, guys, it’s open source, lots of folks contributed including some good folks at Google, no?
Dean Hachamovitch: One of the changes we made to the IE9 JavaScript Engine, codenamed Chakra, to improve performance on real world web sites involves dead code elimination. Yesterday, I filed a bug on a fragile analysis relating to dead code elimination in IE9. Since then, the IE team has released platform preview 7, and updated the IE blog. Dead Code Elimination can be a valid optimization, but i
It’s time for an update on Firefox JS performance. This post will take a look at some benchmark scores, and then dive deeper into what those benchmarks actually measure. Now that JaegerMonkey is available, it’s time for an update on some familiar benchmarks. Contributors to the Mozilla JS engine are making performance improvements throughout the Firefox 4 development cycle, and the progress has be
At the beginning of this year, the Mozilla JavaScript team started a new project, code-named JägerMonkey, with a simple goal: make us fast. Our previous major engine upgrade, TraceMonkey, gave Firefox 3.5 a big speed boost. But while the technology inside TraceMonkey makes it faster than any other engine on certain programs (then and now), it doesn’t help other programs as much. And the web has gr
In new builds of the SpiderMonkey shell we’re introducing an experimental API for parsing JavaScript source code, which landed this week. For now, you have to download and build SpiderMonkey from source to use it, but hopefully we’ll include it in future versions of Firefox. The parser API provides a single function: Reflect.parse(src[, filename=null[, lineno=1]]) Reflect.parse takes a source stri
Here at Mozilla, we have many monkeys. One such effort, JaegerMonkey, is focused on revamping the baseline performance of our JS Engine. That effort is going really well. On the SunSpider benchmark, JaegerMonkey is starting to pull away from the Mozilla trunk’s JS Engine. Both are faster than the engine that ships in Firefox 3.6. JaegerMonkey is not a total rewrite, but it does change some fundame
昨日の夜アップルストア銀座でウェブフォントについて講演しました。 色々な人々に会って、質問も面白かったです。ありがとうございました。 This entry was posted on Thursday, July 1st, 2010 at 3:21 pm and is filed under CSS, Fonts. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Your browser doesn’t support HTML5 video, but you can still watch the video over at YouTube (best viewed in full screen) YouTube Theora 720p WebM 720p In the Firefox 4 nightly builds, and in Firefox 4 Beta 1, we are changing the default tab position so that tabs are on top. This is a preference that users can change by right clicking on any of their toolbars. Moving the default tab position is o
We are marching along in our integration of HBase with the Socorro Crash Stats project, but I wanted to take a minute away from that to talk about a separate project the Metrics team has also been involved with. Mozilla Labs Test Pilot is a project to experiment and analyze data from real world Firefox users to discover quantifiable ways to improve our user experience. I was very interested and e
A Heat Map of the Firefox Menu Bar The Mozilla Labs Test Pilot team recently ran a study to explore how users interact with Firefox’s menu bar. The study is now complete and the raw data is available, so in addition to the great visualizations that they have already made, I put together a heat map: View the full size The data displayed is filtered to only Windows users (since we are now in the pro
After our recent blogs about JägerMonkey, some articles out there gave the impression that we were removing nanojit, throwing everything away, or doing all sorts of other radical things that we are not in fact doing. I don’t have a huge problem with that–this is complicated stuff and it’s hard to get right. So Chris Blizzard made a post correcting some of the misconceptions. I thought it might als
About 2 months ago, we started work on JägerMonkey, a new “baseline” method JIT compiler for SpiderMonkey (and Firefox). The reason we’re doing this is that TraceMonkey is very fast for code that traces well, but for code that doesn’t trace, we’re stuck with the interpreter, which is not fast. The JägerMonkey method JIT will provide a much better performance baseline, and tracing will continue to
I’ve been wanting to write this post for a few years now. During the development of Firefox 3, I worked on the design of the awesome bar (iteration 1, iteration 2), and on the design of Places (an internal name for History and Bookmarks in Firefox). This post details what I’ve imagined as the next chapter for both, but here’s the interesting part: it’s actually the same story. The Fundamentals: S
次のページ
このページを最初にブックマークしてみませんか？
『The Mozilla Blog』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
