5 What's new in WebKitGTK+ 1.3.6?
7 - Update to compile with GTK+ 3.x 2.91.4.
8 - Many, many other bugfixes.
14 What's new in WebKitGTK+ 1.3.5?
16 - Add a HTTP cache implementation. This will be eventually
17 integrated in libsoup itself, but for now it can be accessed from
18 WebKit through the WebKitSoupCache APIs.
19 - Updated to work with GTK+ 3.x 2.91.1.
20 - Add frame-flattening support, used by some mobile browser sto
21 merge all frames in a page into a continuous view.
22 - Many other bugfixes.
28 What's new in WebKitGTK+ 1.3.4?
30 - File reader/writer APIs are now enabled.
31 - The javascript JIT is now enabled by default on ARM.
32 - Clipboard data is no longer lost when the process exists.
34 - GSettings support to save/restore Web Inspector settings.
35 - Add WebSocket support, now enabled by default.
36 - Added WebKitWebView::frame-created signal, emitted when a frame
37 other than the main frame is created in a view.
38 - Added WebKitWebView::view-mode, holding information about how the
39 view is being presented. See the property documentation and
40 http://www.w3.org/TR/view-mode/ for details.
41 - Fullscreen support for HTML5 media player.
42 - Identify as WebKit/Safari in Google domains when
43 enable-site-specific-quirks is activated. Otherwise we'll get a
44 degraded user experience due to their poor UA detection
46 - Added simple media playback options in the context menu for the
48 - Update (and require) to work with gobjet-introspection 0.9.5.
49 - Updated to work with GTK+ 3.x 2.90.7 when in GTK+ 3.x mode.
50 - Make --disable-jit actually work.
51 - Add --enable-opcode-stats configure flag. When enabled, statistics
52 about opcode generation will be printed by JSC.
53 - Many a11y fixes, particularly in the AtkText interface.
54 - CSS box shadows render much faster in many cases.
55 - Many other bugfixes.
61 What's new in WebKitGTK+ 1.3.3?
63 - Fixes to compile with latest GTK+ 2.90.x.
64 - Add support for dropping content in WebKitWebViews.
65 - Many other bugfixes.
71 What's new in WebKitGTK+ 1.3.2?
73 *** This release is an ABI break ***
75 The library has been renamed to libwebkitgtk, so you'll need to
76 recompile your applications when upgrading to 1.3.2.
78 - Add support for GTK+ 3.x. A new configure flag, --with-gtk, has
79 been added, which allows to control which GTK+ version you want to
80 build against. The default value is '2.0', for GTK+ 2.x
81 support. With '3.0' the library will be compiled against GTK+ 3.x
82 (2.90.4 or newer required). In the 3.x mode the .pc file has been
83 renamed from webkit-X.X.pc to webkitgtk-X.X.pc, so you'll need to
84 update your autotools setup accordingly.
85 - Many fixes for the DOM bindings, including support to dispatch
86 events to any Node through webkit_event_target_dispatch_event.
87 - Added a 'inner-node' property to WebKitHitTestResult, carrying the
88 DOM node where the hit test happened.
89 - Many DnD fixes, including a fix for the infamous hang-of-death
90 while dragging the mouse.
91 - Support for <input type="range">.
92 - Many other bugfixes.
98 What's new in WebKitGTK+ 1.3.1?
100 - Initial support for GObject DOM bindings. Present in this release
101 is a substantial subset of the basic DOM APIs (Document, HTML
102 elements, Node, etc) including access to the DOM events through
103 GObject signals. Keep in mind that all the APIs are still
104 unstable, and will probably be subject to changes before the next
106 - Add webkit_web_back_forward_list_clear, to completely clear the
108 - Lots of improvements in DOM clipboard and drag-drop access.
109 - Add support for GTK+ key themes.
110 - Significant improvements in a11y, including improved role support
117 What's new in WebKitGTK+ 1.1.90?
119 - Display server side messages during HTTP auth, since they
120 sometimes contain important information for the authentication
122 - Reduce creation time for WebKitWebView widgets by reusing
123 dictionary structs used for spell-checking instead of creating a
124 new one for each instance.
125 - Implement WebKitWebView::geolocation-policy-decision-requested,
126 emitted when a frame inside the WebView wants to get its position
128 - Add WebKitWebSettings::enable-spatial-navigation to control
129 whether Spatial Navigation is enabled or not. Spatial Navigation
130 allows the user to move through the elements in a page using only
131 the keyboard; this is similar to caret browsing, but with less
132 focus on accessibility since instead of presenting the exact
133 layout of the page to the user a more "logical" way of browsing
134 through its contents is allowed. A specification of this feature
136 http://www.w3.org/TR/WICD/#current-focus-point-algorithm
137 - Add a new build option, --enable-fast-mobile-scrolling. At the
138 moment this only disables fixed backgrounds when there are no
139 other fixed elements in a page, since they generally make
140 scrolling very slow and thus are a big burden in some mobile
142 - GTK+ Input Method support has received a big overhaul, and most of
143 them should work pretty well now.
144 - All known redraw issues in the plugin support (especially with the
145 Java plugin) have been fixed.
146 - Various fixes to the MediaPlayer code to improve responsiveness
147 and avoid lagging on position reporting.
148 - Lots of bugfixes and other improvements.
154 What's new in WebKitGTK+ 1.1.22?
156 - Preliminary support for Java plugins. Basic functionality is
157 there, but there are still a few rough edges. Also newly
158 introduced is a new WebKitWebSetting, 'enable-java-applet', which
159 controls whether WebKit will recognize the non-standard <applet>
161 - Add WebKitWebSettings::auto-resize-window; when enabled, WebKit
162 will act upon the DOM methods that change the size and/or position
163 of the window containing a WebView (window.{moveTo, resizeTo,
165 - Add WebKitWebSettings::enable-file-access-from-file-uris; when
166 enabled, each file:// URI will be assigned its own security
168 - Lots of bugfixes, especially in the PageCache support.
174 What's new in WebKitGTK+ 1.1.21?
176 - New custom-made GStreamer source element that uses the WebCore
177 network layer to download media data; this makes sure any headers
178 and cookies will automatically get added when making requests.
179 - WebKit will now let libsoup know who the first party for a given
180 message is, making it possible to implement accept/deny policies in
182 - The usual stream of fixes, and improvements
188 What's new in WebKitGTK+ 1.1.20?
190 - Fixes to the HTML5 Media Player infrastructure to satisfy sites
191 that require cookies, and Referer to be sent; this makes
192 WebKitGTK+ able to support the new HTML5 support added to Youtube,
193 and Vimeo, for instance.
194 - Windowless plugin support is finally here, making it possible to
195 get plugins to behave on various web pages.
196 - The usual stream of fixes, and improvements
202 What's new in WebKitGTK+ 1.1.19?
204 - Improvements to AtkText implementation
205 - RGBA colormap support has been added
206 - Improvements to the HTML5 media player
207 - Crashes related to clipboard handling, which were hitting many
208 users and seemed to be random have been fixed
214 What's new in WebKitGTK+ 1.1.18?
216 - Add methods to set and get a cache model in WebKitGTK+. We offer
217 two possibilites: document viewer (no caches are used) and browser
218 (similar to the previous defaults).
219 - Add WebKitWebSettings::enable-page-cache. Controls whether the
220 Page Cache is enabled or not. For details about what the page
221 cache is and does see
222 http://webkit.org/blog/427/webkit-page-cache-i-the-basics/
223 The page cache is disabled by default, since the gtk+ port still
224 presents some small bugs when it's enabled.
225 - Add WebKitWebSettings::enable-site-specific-quirks. Controls
226 whether a series of page-specific workarounds are used by WebKit.
227 - Use Content-Encoding support available in libsoup 2.28.2 and
229 - Add WebKitWebSettings::enable-default-context-menu. Controls
230 whether webkitgtk+ will show a default context menu on right click
231 in the view. Note that even with the property set to FALSE right
232 clicks can be handled by the page, either by actions or by
233 ad-hoc in-page context menus.
234 - Make the WebKitWebView::icon-loaded signal carry a string with the
235 favicon's URI. This is an API break, but the signal already had a
236 broken signature and was useless anyway, so it's extremely
237 unlikely that anybody was using it. Also, add the 'icon-uri'
238 property to the view, holding the URI for its current favicon.
239 - Respect Content-Disposition header in downloads (fixes downloads
241 - Various accessibility improvements.
248 What's new in WebKitGTK+ 1.1.17?
250 - New APIs to show and close the web inspector and to inspect an
251 element at the given coordinates.
252 - New property, WebKitWebSettings::tab-key-cycles-through-elements,
253 controls whether TAB is simply interpreted as another keystroke or
254 is used to cycle through the elements in a page.
255 - Many a11y improvements.
256 - The usual amount of random bugfixes.
262 What's new in WebKitGTK+ 1.1.16?
264 - Add optional support to generate the gobject-introspection
265 gir/typelib files. Enable with --enable-introspection, it's off by
267 - Add a new load status value, WEBKIT_LOAD_FAILED, emitted when
268 there's an error during the load process. This is the natural
269 companion to WEBKIT_LOAD_FINISHED, which is only emitted when the
270 load finished succesfuly.
271 - Ensure that keyboard events filtered by GtkIMContext still create
272 the proper DOM events.
273 - Many a11y improvements: caret browsing fixes, expose heading
274 levels, more accessible roles supported, more work in correctly
275 showing the element's ancestry list, improved support for lists,
277 - Many improvements to our media support.
278 - Add a new setting to control DOM pastes
279 (document.execCommand("Paste"))
280 - Many, many bugfixes all over the place.
286 What's new in WebKitGTK+ 1.1.15?
288 - New API to get the subresources from a WebKitWebDataSource. This
289 provides a way of accessing all the resources that compose the
290 view to which the data source is attached.
291 - A new function, webkit_web_view_get_hit_test_result, which allows
292 to do a 'hit test' on the coordinates specified by a mouse
293 event. A hit test provides context information about that point in
294 the document, like whether it's an image, a link, an input box,
296 - Our DumpRenderTree implementation now supports eventSender, which
297 allows us to run many more LayoutTests and make WebKitGTK+ more
298 stable and feature-complete.
299 - JSNES runs 6x faster: http://trac.webkit.org/changeset/48573
300 - The usual small improvements and bugfixes.
306 What's new in WebKitGTK+ 1.1.14?
308 - New API has been added to WebKitWebFrame to allow applying
309 scrollbars policy as requested by web applications to the main
310 frame; if the parent of the WebKitWebView widget is a
311 GtkScrolledWindow, policy is applied by the default handler.
312 - A new API has been added to help dealing with the various
313 resources that are downloaded to compose the final rendering; you
314 can now obtain the source code for a page that is loaded, for
316 - A new property has been added to WebKitWebView to allow setting it
317 to "View Source" mode.
318 - HTML5 database has gained API to manage the individual databases,
319 including usage and quota.
320 - A new signal `resource-request-starting' has been added to the
321 WebKitWebView to allow modification of outgoing requests for every
323 - Connection limit has been increased to 60 total connections, 6
324 per-host, matching other browsers more closely; this seems to have
325 improved loading time of some sites.
326 - Undo/redo support has been added to editable texts.
327 - The usual stream of small improvements and bug fixes.
333 What's new in WebKitGTK+ 1.1.13?
335 - GNOME Keyring support was removed in favor of the new Password
336 Manager soup feature; to get exactly the same behavior,
337 applications should use SoupPasswordManagerGNOME. This requires
338 libsoup 2.27.91 or newer.
339 - Several accessibility improvements, including support for testing
340 the a11y infrastructure in our layout tests.
341 - You can now enable/disable HTML5 offline application cache using a
342 new setting added to WebKitWebSettings.
343 - Drag support has landed, meaning you can start playing with HTML5
344 drag and drop support; drop support is still missing.
345 - A crash with scripts closing windows has been fixed.
346 - Image cursors support has been added.
347 - The usual stream of small improvements and bug fixes.
353 What's new in WebKitGTK+ 1.1.12?
355 - Fix WebKitSoupAuthDialog to only save passwords in gnome-keyring
356 (if enabled) when authentication succeeds.
357 - Implement a proper size_request method for WebKitWebView. The
358 widget will request the size of the whole page as its size
360 - Many a11y improvements.
361 - The usual amount of other misc fixes.
362 - WEBKIT_DEBUG variable now accepts channel names in any case
369 What's new in WebKitGTK+ 1.1.11?
371 - WebKit has got a new feature - a XSS auditor, that should improve
372 security; this feature is still experimental, and disabled by
373 default, but applications can enable it using the setting.
374 - The hackish content sniffing code that was beig used to avoid
375 pages requesting downloads instead of displaying content has been
376 replaced by usage of a new Soup feature, which implements proper
378 - More accessibility work, including fixes for problems which were
379 critical for a possible GNOME 2.28 release.
380 - Pasting rich text from other browsers should now work as expected.
381 - The usual amount of misc fixes.
387 What's new in WebKitGTK+ 1.1.10?
389 - WebKitNetworkRequest has now GObject properties for its URI and
390 the SoupMessage that backs it up.
391 - Fix AtkText methods get_selection and get_n_selections to not use
392 the global selection but only the selection that belongs to the
394 - Fix a crasher when emitting the a11y signal 'text-caret-moved' in
395 some situations with debug builds.
401 What's new in WebKitGTK+ 1.1.9?
403 - Scrolling once again received a lot of love, and many subtle
404 problems and bugs were killed, and we now get correct behavior in
405 acid2; a number of smaller improvements are in the queue.
406 - Accessibility keeps gaining better support. On this release a lot
407 of work was done on the AtkText interface implementation.
408 - WebKitNetworkRequest now carries with it all the information
409 regarding the request, not only the URI. This means you will no
410 longer miss headers such as Referer when passing NetworkRequest
411 objects from a callback to webkit_web_frame_load_request.
417 What's new in WebKitGTK+ 1.1.8?
419 - We found out that WebKitWebHistoryItems were being kept with a
420 reference count of 2 instead of 1 as they should; nobody should be
421 relying on that, but if you hit reference counting problems with
422 items you were creating yourself, this is for you.
423 - You can now copy images from the web page to the clipboard.
424 - Improvements were made to the Plugin handling code.
425 - Scroll events will now be correctly reported to web applications.
426 - You can now embed arbitrary widgets as if it was a plugin, with
427 the new "create-plugin-widget" signal.
428 - The atk_text_get_text_{at,after,before}_offset methods are now
429 implemented for all boundary types except LINE_AFTER and
431 - The usual stream of minor fixes and improvements, as always.
437 What's new in WebKitGTK+ 1.1.7?
439 - This release includes a security fix:
440 SVGList::insertItemBefore would not perform a bounds check on the
441 index it was provided, potentially leading to a buffer overflow.
442 - New frame loading properties supersede various load-* signals, and
443 are also accessible in the WebView, for convenience, making this
445 - JIT is now supported for X86-64 on Linux, and enabled by default!
446 - A regression on webkit_web_view_load_string has been fixed, making
447 it work correctly again when the document uses encodings which may
448 use more than 1 byte per character.
449 - Yet more work has been done to the ATK support, caret browsing
450 support improvements in particular.
451 - Filenames suggested by the Download functionality now correctly
452 use the filename given by the host, if available.
453 - Build fixes for IA64, and AMD64
454 - gtk-doc support has also improved, and you should now be able to
455 cd WebKit/gtk/docs and type make docs, if you --enable-gtk-doc on
456 configure, as long as you build with srcdir == builddir.
457 - More crashes and other bugs fixed, and small improvements made
464 What's new in WebKitGTK+ 1.1.6?
466 - Several ATK support additions and fixes got landed, with many
467 roles being now implemented, providing better accessibility.
468 - Caret browsing is now available.
469 - Spelling check has been implemented using Enchant; the API is
470 still lacking, and some of the functionality still needs to be
472 - Error reporting is now available, with default error pages, and
473 API that allows the application to override the default behavior;
474 localization of those pages is still not supported, but planned.
475 - More crashes and other bugs fixed.
481 What's new in WebKitGTK+ 1.1.5?
483 - Added gtk-doc support to the build system. It is not fully
484 integrated yet, so some manual tweaking is still needed.
485 - Minimum required GTK+ version is now 2.10.
486 - Added l10n support with gettext. Translations are stored in
488 - Many improvements to the ATK support. It's good enough to provide
489 a basic user experience with Accerciser now, but we'll keep
490 improving it in further releases.
491 - New printing API that allows applications to control and monitor
492 the printing process, when requested by javascript or started by
500 What's new in WebKitGTK+ 1.1.4?
502 - WebKitWebView gained uri and title properties, deprecating the
503 usage of the title-changed signal.
504 - Basic functionality for HTML5 media tags has been achieved; there
505 are many unimplented methods, and rough edges still, though.
506 - Font rendering received quite some love, with layouting, and
507 memory handling fixes, and at least one less crash.
508 - A new signal, new-window-policy-decision-requested, has been added
509 to WebKitWebView, that makes it possible for the application to
510 correctly decide what to do when new windows are requested.
511 - A bug that made tooltips for consecutive links not update their
513 - Several improvements were made to the HTTP backend, including
514 making it more robust when talking to servers which send bad
515 Content-Type headers.
516 - WebKitWebView now uses the GtkBinding system to handle key events,
517 which means that the user is now able to customize the keys used
518 for various operations, and that many subtle bugs have been fixed.
524 The 1.1.3 release was just a quick bug fix release, because we made a
525 mistake in library versioning.
531 What's new in WebKitGTK+ 1.1.2?
533 - Added support for downloads: a new signal, 'download-requested',
534 will be emitted by WebKit when a dowload is requested. On top of
535 that, the download process has been encapsulated in a new object,
536 WebKitDownload, which allows the user to control it or to start
537 new downloads from the client side.
538 - Added webkit_web_view_get_encoding to get the automatic encoding
540 - Added GObject properties for 'encoding' and 'custom-encoding'.
541 - Added 'javascript-profiling-enabled' property to the WebInspector,
542 which allows to enable and disable the profiling functionality.
543 - Added API to create and add history items to WebKit's history.
544 - Improved debugging support with WEBKIT_DEBUG environment
545 variable. Most of the settings will only give useful output for
546 debug builds, but WEBKIT_DEBUG=Network will log all HTTP traffic
547 form libsoup to console. See WebCore/platform/gtk/LoggingGtk.cpp
548 for all the options available.
555 What's new in WebKitGTK+ 1.1.1?
557 - ABI compatibility with 1.0.3 was broken, so you will need to
558 recompile your application against 1.1.1
559 - Support for the CURL backend was dropped, libsoup is the only HTTP
561 - webkit_get_default_session, to get the SoupSession used internally
563 - 'create-web-view' signal, emitted when the creation of a new
565 - 'navigation-policy-decision-requested' signal, emitted when a
566 navigation to another page is requested.
567 - 'mime-type-policy-decision-requested' signal, emitted each time
568 WebKit is about to show a URI with a given MIME type.
569 - Support for the Web Inspector
570 (see http://webkit.org/blog/197/web-inspector-redesign/)
571 - HTTP authentication support, with optional gnome-keyring storage.
572 - New load functions: webkit_web_view_open, webkit_web_view_load_uri
573 and webkit_web_view_load_request. The old
574 webkit_web_view_load_string and webkit_web_view_load_html_string
576 - webkit_web_view_reload_bypass_cache
577 - webkit_web_view_{get,set}_custom_encoding, to override the
578 encoding of the current page.
579 - Improved stability and lots of bugfixes.