5 What's new in WebKitGTK+ 1.1.90?
7 - Display server side messages during HTTP auth, since they
8 sometimes contain important information for the authentication
10 - Reduce creation time for WebKitWebView widgets by reusing
11 dictionary structs used for spell-checking instead of creating a
12 new one for each instance.
13 - Implement WebKitWebView::geolocation-policy-decision-requested,
14 emitted when a frame inside the WebView wants to get its position
16 - Add WebKitWebSettings::enable-spatial-navigation to control
17 whether Spatial Navigation is enabled or not. Spatial Navigation
18 allows the user to move through the elements in a page using only
19 the keyboard; this is similar to caret browsing, but with less
20 focus on accessibility since instead of presenting the exact
21 layout of the page to the user a more "logical" way of browsing
22 through its contents is allowed. A specification of this feature
24 http://www.w3.org/TR/WICD/#current-focus-point-algorithm
25 - Add a new build option, --enable-fast-mobile-scrolling. At the
26 moment this only disables fixed backgrounds when there are no
27 other fixed elements in a page, since they generally make
28 scrolling very slow and thus are a big burden in some mobile
30 - GTK+ Input Method support has received a big overhaul, and most of
31 them should work pretty well now.
32 - All known redraw issues in the plugin support (especially with the
33 Java plugin) have been fixed.
34 - Various fixes to the MediaPlayer code to improve responsiveness
35 and avoid lagging on position reporting.
36 - Lots of bugfixes and other improvements.
42 What's new in WebKitGTK+ 1.1.22?
44 - Preliminary support for Java plugins. Basic functionality is
45 there, but there are still a few rough edges. Also newly
46 introduced is a new WebKitWebSetting, 'enable-java-applet', which
47 controls whether WebKit will recognize the non-standard <applet>
49 - Add WebKitWebSettings::auto-resize-window; when enabled, WebKit
50 will act upon the DOM methods that change the size and/or position
51 of the window containing a WebView (window.{moveTo, resizeTo,
53 - Add WebKitWebSettings::enable-file-access-from-file-uris; when
54 enabled, each file:// URI will be assigned its own security
56 - Lots of bugfixes, especially in the PageCache support.
62 What's new in WebKitGTK+ 1.1.21?
64 - New custom-made GStreamer source element that uses the WebCore
65 network layer to download media data; this makes sure any headers
66 and cookies will automatically get added when making requests.
67 - WebKit will now let libsoup know who the first party for a given
68 message is, making it possible to implement accept/deny policies in
70 - The usual stream of fixes, and improvements
76 What's new in WebKitGTK+ 1.1.20?
78 - Fixes to the HTML5 Media Player infrastructure to satisfy sites
79 that require cookies, and Referer to be sent; this makes
80 WebKitGTK+ able to support the new HTML5 support added to Youtube,
81 and Vimeo, for instance.
82 - Windowless plugin support is finally here, making it possible to
83 get plugins to behave on various web pages.
84 - The usual stream of fixes, and improvements
90 What's new in WebKitGTK+ 1.1.19?
92 - Improvements to AtkText implementation
93 - RGBA colormap support has been added
94 - Improvements to the HTML5 media player
95 - Crashes related to clipboard handling, which were hitting many
96 users and seemed to be random have been fixed
102 What's new in WebKitGTK+ 1.1.18?
104 - Add methods to set and get a cache model in WebKitGTK+. We offer
105 two possibilites: document viewer (no caches are used) and browser
106 (similar to the previous defaults).
107 - Add WebKitWebSettings::enable-page-cache. Controls whether the
108 Page Cache is enabled or not. For details about what the page
109 cache is and does see
110 http://webkit.org/blog/427/webkit-page-cache-i-the-basics/
111 The page cache is disabled by default, since the gtk+ port still
112 presents some small bugs when it's enabled.
113 - Add WebKitWebSettings::enable-site-specific-quirks. Controls
114 whether a series of page-specific workarounds are used by WebKit.
115 - Use Content-Encoding support available in libsoup 2.28.2 and
117 - Add WebKitWebSettings::enable-default-context-menu. Controls
118 whether webkitgtk+ will show a default context menu on right click
119 in the view. Note that even with the property set to FALSE right
120 clicks can be handled by the page, either by actions or by
121 ad-hoc in-page context menus.
122 - Make the WebKitWebView::icon-loaded signal carry a string with the
123 favicon's URI. This is an API break, but the signal already had a
124 broken signature and was useless anyway, so it's extremely
125 unlikely that anybody was using it. Also, add the 'icon-uri'
126 property to the view, holding the URI for its current favicon.
127 - Respect Content-Disposition header in downloads (fixes downloads
129 - Various accessibility improvements.
136 What's new in WebKitGTK+ 1.1.17?
138 - New APIs to show and close the web inspector and to inspect an
139 element at the given coordinates.
140 - New property, WebKitWebSettings::tab-key-cycles-through-elements,
141 controls whether TAB is simply interpreted as another keystroke or
142 is used to cycle through the elements in a page.
143 - Many a11y improvements.
144 - The usual amount of random bugfixes.
150 What's new in WebKitGTK+ 1.1.16?
152 - Add optional support to generate the gobject-introspection
153 gir/typelib files. Enable with --enable-introspection, it's off by
155 - Add a new load status value, WEBKIT_LOAD_FAILED, emitted when
156 there's an error during the load process. This is the natural
157 companion to WEBKIT_LOAD_FINISHED, which is only emitted when the
158 load finished succesfuly.
159 - Ensure that keyboard events filtered by GtkIMContext still create
160 the proper DOM events.
161 - Many a11y improvements: caret browsing fixes, expose heading
162 levels, more accessible roles supported, more work in correctly
163 showing the element's ancestry list, improved support for lists,
165 - Many improvements to our media support.
166 - Add a new setting to control DOM pastes
167 (document.execCommand("Paste"))
168 - Many, many bugfixes all over the place.
174 What's new in WebKitGTK+ 1.1.15?
176 - New API to get the subresources from a WebKitWebDataSource. This
177 provides a way of accessing all the resources that compose the
178 view to which the data source is attached.
179 - A new function, webkit_web_view_get_hit_test_result, which allows
180 to do a 'hit test' on the coordinates specified by a mouse
181 event. A hit test provides context information about that point in
182 the document, like whether it's an image, a link, an input box,
184 - Our DumpRenderTree implementation now supports eventSender, which
185 allows us to run many more LayoutTests and make WebKitGTK+ more
186 stable and feature-complete.
187 - JSNES runs 6x faster: http://trac.webkit.org/changeset/48573
188 - The usual small improvements and bugfixes.
194 What's new in WebKitGTK+ 1.1.14?
196 - New API has been added to WebKitWebFrame to allow applying
197 scrollbars policy as requested by web applications to the main
198 frame; if the parent of the WebKitWebView widget is a
199 GtkScrolledWindow, policy is applied by the default handler.
200 - A new API has been added to help dealing with the various
201 resources that are downloaded to compose the final rendering; you
202 can now obtain the source code for a page that is loaded, for
204 - A new property has been added to WebKitWebView to allow setting it
205 to "View Source" mode.
206 - HTML5 database has gained API to manage the individual databases,
207 including usage and quota.
208 - A new signal `resource-request-starting' has been added to the
209 WebKitWebView to allow modification of outgoing requests for every
211 - Connection limit has been increased to 60 total connections, 6
212 per-host, matching other browsers more closely; this seems to have
213 improved loading time of some sites.
214 - Undo/redo support has been added to editable texts.
215 - The usual stream of small improvements and bug fixes.
221 What's new in WebKitGTK+ 1.1.13?
223 - GNOME Keyring support was removed in favor of the new Password
224 Manager soup feature; to get exactly the same behavior,
225 applications should use SoupPasswordManagerGNOME. This requires
226 libsoup 2.27.91 or newer.
227 - Several accessibility improvements, including support for testing
228 the a11y infrastructure in our layout tests.
229 - You can now enable/disable HTML5 offline application cache using a
230 new setting added to WebKitWebSettings.
231 - Drag support has landed, meaning you can start playing with HTML5
232 drag and drop support; drop support is still missing.
233 - A crash with scripts closing windows has been fixed.
234 - Image cursors support has been added.
235 - The usual stream of small improvements and bug fixes.
241 What's new in WebKitGTK+ 1.1.12?
243 - Fix WebKitSoupAuthDialog to only save passwords in gnome-keyring
244 (if enabled) when authentication succeeds.
245 - Implement a proper size_request method for WebKitWebView. The
246 widget will request the size of the whole page as its size
248 - Many a11y improvements.
249 - The usual amount of other misc fixes.
250 - WEBKIT_DEBUG variable now accepts channel names in any case
257 What's new in WebKitGTK+ 1.1.11?
259 - WebKit has got a new feature - a XSS auditor, that should improve
260 security; this feature is still experimental, and disabled by
261 default, but applications can enable it using the setting.
262 - The hackish content sniffing code that was beig used to avoid
263 pages requesting downloads instead of displaying content has been
264 replaced by usage of a new Soup feature, which implements proper
266 - More accessibility work, including fixes for problems which were
267 critical for a possible GNOME 2.28 release.
268 - Pasting rich text from other browsers should now work as expected.
269 - The usual amount of misc fixes.
275 What's new in WebKitGTK+ 1.1.10?
277 - WebKitNetworkRequest has now GObject properties for its URI and
278 the SoupMessage that backs it up.
279 - Fix AtkText methods get_selection and get_n_selections to not use
280 the global selection but only the selection that belongs to the
282 - Fix a crasher when emitting the a11y signal 'text-caret-moved' in
283 some situations with debug builds.
289 What's new in WebKitGTK+ 1.1.9?
291 - Scrolling once again received a lot of love, and many subtle
292 problems and bugs were killed, and we now get correct behavior in
293 acid2; a number of smaller improvements are in the queue.
294 - Accessibility keeps gaining better support. On this release a lot
295 of work was done on the AtkText interface implementation.
296 - WebKitNetworkRequest now carries with it all the information
297 regarding the request, not only the URI. This means you will no
298 longer miss headers such as Referer when passing NetworkRequest
299 objects from a callback to webkit_web_frame_load_request.
305 What's new in WebKitGTK+ 1.1.8?
307 - We found out that WebKitWebHistoryItems were being kept with a
308 reference count of 2 instead of 1 as they should; nobody should be
309 relying on that, but if you hit reference counting problems with
310 items you were creating yourself, this is for you.
311 - You can now copy images from the web page to the clipboard.
312 - Improvements were made to the Plugin handling code.
313 - Scroll events will now be correctly reported to web applications.
314 - You can now embed arbitrary widgets as if it was a plugin, with
315 the new "create-plugin-widget" signal.
316 - The atk_text_get_text_{at,after,before}_offset methods are now
317 implemented for all boundary types except LINE_AFTER and
319 - The usual stream of minor fixes and improvements, as always.
325 What's new in WebKitGTK+ 1.1.7?
327 - This release includes a security fix:
328 SVGList::insertItemBefore would not perform a bounds check on the
329 index it was provided, potentially leading to a buffer overflow.
330 - New frame loading properties supersede various load-* signals, and
331 are also accessible in the WebView, for convenience, making this
333 - JIT is now supported for X86-64 on Linux, and enabled by default!
334 - A regression on webkit_web_view_load_string has been fixed, making
335 it work correctly again when the document uses encodings which may
336 use more than 1 byte per character.
337 - Yet more work has been done to the ATK support, caret browsing
338 support improvements in particular.
339 - Filenames suggested by the Download functionality now correctly
340 use the filename given by the host, if available.
341 - Build fixes for IA64, and AMD64
342 - gtk-doc support has also improved, and you should now be able to
343 cd WebKit/gtk/docs and type make docs, if you --enable-gtk-doc on
344 configure, as long as you build with srcdir == builddir.
345 - More crashes and other bugs fixed, and small improvements made
352 What's new in WebKitGTK+ 1.1.6?
354 - Several ATK support additions and fixes got landed, with many
355 roles being now implemented, providing better accessibility.
356 - Caret browsing is now available.
357 - Spelling check has been implemented using Enchant; the API is
358 still lacking, and some of the functionality still needs to be
360 - Error reporting is now available, with default error pages, and
361 API that allows the application to override the default behavior;
362 localization of those pages is still not supported, but planned.
363 - More crashes and other bugs fixed.
369 What's new in WebKitGTK+ 1.1.5?
371 - Added gtk-doc support to the build system. It is not fully
372 integrated yet, so some manual tweaking is still needed.
373 - Minimum required GTK+ version is now 2.10.
374 - Added l10n support with gettext. Translations are stored in
376 - Many improvements to the ATK support. It's good enough to provide
377 a basic user experience with Accerciser now, but we'll keep
378 improving it in further releases.
379 - New printing API that allows applications to control and monitor
380 the printing process, when requested by javascript or started by
388 What's new in WebKitGTK+ 1.1.4?
390 - WebKitWebView gained uri and title properties, deprecating the
391 usage of the title-changed signal.
392 - Basic functionality for HTML5 media tags has been achieved; there
393 are many unimplented methods, and rough edges still, though.
394 - Font rendering received quite some love, with layouting, and
395 memory handling fixes, and at least one less crash.
396 - A new signal, new-window-policy-decision-requested, has been added
397 to WebKitWebView, that makes it possible for the application to
398 correctly decide what to do when new windows are requested.
399 - A bug that made tooltips for consecutive links not update their
401 - Several improvements were made to the HTTP backend, including
402 making it more robust when talking to servers which send bad
403 Content-Type headers.
404 - WebKitWebView now uses the GtkBinding system to handle key events,
405 which means that the user is now able to customize the keys used
406 for various operations, and that many subtle bugs have been fixed.
412 The 1.1.3 release was just a quick bug fix release, because we made a
413 mistake in library versioning.
419 What's new in WebKitGTK+ 1.1.2?
421 - Added support for downloads: a new signal, 'download-requested',
422 will be emitted by WebKit when a dowload is requested. On top of
423 that, the download process has been encapsulated in a new object,
424 WebKitDownload, which allows the user to control it or to start
425 new downloads from the client side.
426 - Added webkit_web_view_get_encoding to get the automatic encoding
428 - Added GObject properties for 'encoding' and 'custom-encoding'.
429 - Added 'javascript-profiling-enabled' property to the WebInspector,
430 which allows to enable and disable the profiling functionality.
431 - Added API to create and add history items to WebKit's history.
432 - Improved debugging support with WEBKIT_DEBUG environment
433 variable. Most of the settings will only give useful output for
434 debug builds, but WEBKIT_DEBUG=Network will log all HTTP traffic
435 form libsoup to console. See WebCore/platform/gtk/LoggingGtk.cpp
436 for all the options available.
443 What's new in WebKitGTK+ 1.1.1?
445 - ABI compatibility with 1.0.3 was broken, so you will need to
446 recompile your application against 1.1.1
447 - Support for the CURL backend was dropped, libsoup is the only HTTP
449 - webkit_get_default_session, to get the SoupSession used internally
451 - 'create-web-view' signal, emitted when the creation of a new
453 - 'navigation-policy-decision-requested' signal, emitted when a
454 navigation to another page is requested.
455 - 'mime-type-policy-decision-requested' signal, emitted each time
456 WebKit is about to show a URI with a given MIME type.
457 - Support for the Web Inspector
458 (see http://webkit.org/blog/197/web-inspector-redesign/)
459 - HTTP authentication support, with optional gnome-keyring storage.
460 - New load functions: webkit_web_view_open, webkit_web_view_load_uri
461 and webkit_web_view_load_request. The old
462 webkit_web_view_load_string and webkit_web_view_load_html_string
464 - webkit_web_view_reload_bypass_cache
465 - webkit_web_view_{get,set}_custom_encoding, to override the
466 encoding of the current page.
467 - Improved stability and lots of bugfixes.