1 ================= 2 WebKitGTK+ 1.1.21 3 ================= 4 5 What's new in WebKitGTK+ 1.1.21? 6 7 - New custom-made GStreamer source element that uses the WebCore 8 network layer to download media data; this makes sure any headers 9 and cookies will automatically get added when making requests. 10 - WebKit will now let libsoup know who the first party for a given 11 message is, making it possible to implement accept/deny policies in 12 Soup. 13 - The usual stream of fixes, and improvements 14 15 ================= 16 WebKitGTK+ 1.1.20 17 ================= 18 19 What's new in WebKitGTK+ 1.1.20? 20 21 - Fixes to the HTML5 Media Player infrastructure to satisfy sites 22 that require cookies, and Referer to be sent; this makes 23 WebKitGTK+ able to support the new HTML5 support added to Youtube, 24 and Vimeo, for instance. 25 - Windowless plugin support is finally here, making it possible to 26 get plugins to behave on various web pages. 27 - The usual stream of fixes, and improvements 28 29 ================= 30 WebKitGTK+ 1.1.19 31 ================= 32 33 What's new in WebKitGTK+ 1.1.19? 34 35 - Improvements to AtkText implementation 36 - RGBA colormap support has been added 37 - Improvements to the HTML5 media player 38 - Crashes related to clipboard handling, which were hitting many 39 users and seemed to be random have been fixed 40 41 ================= 42 WebKitGTK+ 1.1.18 43 ================= 44 45 What's new in WebKitGTK+ 1.1.18? 46 47 - Add methods to set and get a cache model in WebKitGTK+. We offer 48 two possibilites: document viewer (no caches are used) and browser 49 (similar to the previous defaults). 50 - Add WebKitWebSettings::enable-page-cache. Controls whether the 51 Page Cache is enabled or not. For details about what the page 52 cache is and does see 53 http://webkit.org/blog/427/webkit-page-cache-i-the-basics/ 54 The page cache is disabled by default, since the gtk+ port still 55 presents some small bugs when it's enabled. 56 - Add WebKitWebSettings::enable-site-specific-quirks. Controls 57 whether a series of page-specific workarounds are used by WebKit. 58 - Use Content-Encoding support available in libsoup 2.28.2 and 59 newer. 60 - Add WebKitWebSettings::enable-default-context-menu. Controls 61 whether webkitgtk+ will show a default context menu on right click 62 in the view. Note that even with the property set to FALSE right 63 clicks can be handled by the page, either by actions or by 64 ad-hoc in-page context menus. 65 - Make the WebKitWebView::icon-loaded signal carry a string with the 66 favicon's URI. This is an API break, but the signal already had a 67 broken signature and was useless anyway, so it's extremely 68 unlikely that anybody was using it. Also, add the 'icon-uri' 69 property to the view, holding the URI for its current favicon. 70 - Respect Content-Disposition header in downloads (fixes downloads 71 in gmail). 72 - Various accessibility improvements. 73 - Many bugfixes. 74 75 ================= 76 WebKitGTK+ 1.1.17 77 ================= 78 79 What's new in WebKitGTK+ 1.1.17? 80 81 - New APIs to show and close the web inspector and to inspect an 82 element at the given coordinates. 83 - New property, WebKitWebSettings::tab-key-cycles-through-elements, 84 controls whether TAB is simply interpreted as another keystroke or 85 is used to cycle through the elements in a page. 86 - Many a11y improvements. 87 - The usual amount of random bugfixes. 88 89 ================= 90 WebKitGTK+ 1.1.16 91 ================= 92 93 What's new in WebKitGTK+ 1.1.16? 94 95 - Add optional support to generate the gobject-introspection 96 gir/typelib files. Enable with --enable-introspection, it's off by 97 default. 98 - Add a new load status value, WEBKIT_LOAD_FAILED, emitted when 99 there's an error during the load process. This is the natural 100 companion to WEBKIT_LOAD_FINISHED, which is only emitted when the 101 load finished succesfuly. 102 - Ensure that keyboard events filtered by GtkIMContext still create 103 the proper DOM events. 104 - Many a11y improvements: caret browsing fixes, expose heading 105 levels, more accessible roles supported, more work in correctly 106 showing the element's ancestry list, improved support for lists, 107 etc. 108 - Many improvements to our media support. 109 - Add a new setting to control DOM pastes 110 (document.execCommand("Paste")) 111 - Many, many bugfixes all over the place. 112 113 ================= 114 WebKitGTK+ 1.1.15 115 ================= 116 117 What's new in WebKitGTK+ 1.1.15? 118 119 - New API to get the subresources from a WebKitWebDataSource. This 120 provides a way of accessing all the resources that compose the 121 view to which the data source is attached. 122 - A new function, webkit_web_view_get_hit_test_result, which allows 123 to do a 'hit test' on the coordinates specified by a mouse 124 event. A hit test provides context information about that point in 125 the document, like whether it's an image, a link, an input box, 126 etc. 127 - Our DumpRenderTree implementation now supports eventSender, which 128 allows us to run many more LayoutTests and make WebKitGTK+ more 129 stable and feature-complete. 130 - JSNES runs 6x faster: http://trac.webkit.org/changeset/48573 131 - The usual small improvements and bugfixes. 132 133 ================= 134 WebKitGTK+ 1.1.14 135 ================= 136 137 What's new in WebKitGTK+ 1.1.14? 138 139 - New API has been added to WebKitWebFrame to allow applying 140 scrollbars policy as requested by web applications to the main 141 frame; if the parent of the WebKitWebView widget is a 142 GtkScrolledWindow, policy is applied by the default handler. 143 - A new API has been added to help dealing with the various 144 resources that are downloaded to compose the final rendering; you 145 can now obtain the source code for a page that is loaded, for 146 instance. 147 - A new property has been added to WebKitWebView to allow setting it 148 to "View Source" mode. 149 - HTML5 database has gained API to manage the individual databases, 150 including usage and quota. 151 - A new signal `resource-request-starting' has been added to the 152 WebKitWebView to allow modification of outgoing requests for every 153 resource. 154 - Connection limit has been increased to 60 total connections, 6 155 per-host, matching other browsers more closely; this seems to have 156 improved loading time of some sites. 157 - Undo/redo support has been added to editable texts. 158 - The usual stream of small improvements and bug fixes. 159 160 ================= 161 WebKitGTK+ 1.1.13 162 ================= 163 164 What's new in WebKitGTK+ 1.1.13? 165 166 - GNOME Keyring support was removed in favor of the new Password 167 Manager soup feature; to get exactly the same behavior, 168 applications should use SoupPasswordManagerGNOME. This requires 169 libsoup 2.27.91 or newer. 170 - Several accessibility improvements, including support for testing 171 the a11y infrastructure in our layout tests. 172 - You can now enable/disable HTML5 offline application cache using a 173 new setting added to WebKitWebSettings. 174 - Drag support has landed, meaning you can start playing with HTML5 175 drag and drop support; drop support is still missing. 176 - A crash with scripts closing windows has been fixed. 177 - Image cursors support has been added. 178 - The usual stream of small improvements and bug fixes. 179 180 ================= 181 WebKitGTK+ 1.1.12 182 ================= 183 184 What's new in WebKitGTK+ 1.1.12? 185 186 - Fix WebKitSoupAuthDialog to only save passwords in gnome-keyring 187 (if enabled) when authentication succeeds. 188 - Implement a proper size_request method for WebKitWebView. The 189 widget will request the size of the whole page as its size 190 requisition. 191 - Many a11y improvements. 192 - The usual amount of other misc fixes. 193 - WEBKIT_DEBUG variable now accepts channel names in any case 194 again. 195 196 ================= 197 WebKitGTK+ 1.1.11 198 ================= 199 200 What's new in WebKitGTK+ 1.1.11? 201 202 - WebKit has got a new feature - a XSS auditor, that should improve 203 security; this feature is still experimental, and disabled by 204 default, but applications can enable it using the setting. 205 - The hackish content sniffing code that was beig used to avoid 206 pages requesting downloads instead of displaying content has been 207 replaced by usage of a new Soup feature, which implements proper 208 content sniffing. 209 - More accessibility work, including fixes for problems which were 210 critical for a possible GNOME 2.28 release. 211 - Pasting rich text from other browsers should now work as expected. 212 - The usual amount of misc fixes. 213 214 ================= 215 WebKitGTK+ 1.1.10 216 ================= 217 218 What's new in WebKitGTK+ 1.1.10? 219 220 - WebKitNetworkRequest has now GObject properties for its URI and 221 the SoupMessage that backs it up. 222 - Fix AtkText methods get_selection and get_n_selections to not use 223 the global selection but only the selection that belongs to the 224 object being used. 225 - Fix a crasher when emitting the a11y signal 'text-caret-moved' in 226 some situations with debug builds. 227 228 ================ 229 WebKitGTK+ 1.1.9 230 ================ 231 232 What's new in WebKitGTK+ 1.1.9? 233 234 - Scrolling once again received a lot of love, and many subtle 235 problems and bugs were killed, and we now get correct behavior in 236 acid2; a number of smaller improvements are in the queue. 237 - Accessibility keeps gaining better support. On this release a lot 238 of work was done on the AtkText interface implementation. 239 - WebKitNetworkRequest now carries with it all the information 240 regarding the request, not only the URI. This means you will no 241 longer miss headers such as Referer when passing NetworkRequest 242 objects from a callback to webkit_web_frame_load_request. 243 244 ================ 245 WebKitGTK+ 1.1.8 246 ================ 247 248 What's new in WebKitGTK+ 1.1.8? 249 250 - We found out that WebKitWebHistoryItems were being kept with a 251 reference count of 2 instead of 1 as they should; nobody should be 252 relying on that, but if you hit reference counting problems with 253 items you were creating yourself, this is for you. 254 - You can now copy images from the web page to the clipboard. 255 - Improvements were made to the Plugin handling code. 256 - Scroll events will now be correctly reported to web applications. 257 - You can now embed arbitrary widgets as if it was a plugin, with 258 the new "create-plugin-widget" signal. 259 - The atk_text_get_text_{at,after,before}_offset methods are now 260 implemented for all boundary types except LINE_AFTER and 261 LINE_BEFORE. 262 - The usual stream of minor fixes and improvements, as always. 263 264 ================ 265 WebKitGTK+ 1.1.7 266 ================ 267 268 What's new in WebKitGTK+ 1.1.7? 269 270 - This release includes a security fix: 271 SVGList::insertItemBefore would not perform a bounds check on the 272 index it was provided, potentially leading to a buffer overflow. 273 - New frame loading properties supersede various load-* signals, and 274 are also accessible in the WebView, for convenience, making this 275 API saner. 276 - JIT is now supported for X86-64 on Linux, and enabled by default! 277 - A regression on webkit_web_view_load_string has been fixed, making 278 it work correctly again when the document uses encodings which may 279 use more than 1 byte per character. 280 - Yet more work has been done to the ATK support, caret browsing 281 support improvements in particular. 282 - Filenames suggested by the Download functionality now correctly 283 use the filename given by the host, if available. 284 - Build fixes for IA64, and AMD64 285 - gtk-doc support has also improved, and you should now be able to 286 cd WebKit/gtk/docs and type make docs, if you --enable-gtk-doc on 287 configure, as long as you build with srcdir == builddir. 288 - More crashes and other bugs fixed, and small improvements made 289 under the hood. 290 291 ================ 292 WebKitGTK+ 1.1.6 293 ================ 294 295 What's new in WebKitGTK+ 1.1.6? 296 297 - Several ATK support additions and fixes got landed, with many 298 roles being now implemented, providing better accessibility. 299 - Caret browsing is now available. 300 - Spelling check has been implemented using Enchant; the API is 301 still lacking, and some of the functionality still needs to be 302 improved, though. 303 - Error reporting is now available, with default error pages, and 304 API that allows the application to override the default behavior; 305 localization of those pages is still not supported, but planned. 306 - More crashes and other bugs fixed. 307 308 ================ 309 WebKitGTK+ 1.1.5 310 ================ 311 312 What's new in WebKitGTK+ 1.1.5? 313 314 - Added gtk-doc support to the build system. It is not fully 315 integrated yet, so some manual tweaking is still needed. 316 - Minimum required GTK+ version is now 2.10. 317 - Added l10n support with gettext. Translations are stored in 318 WebKit/gtk/po/. 319 - Many improvements to the ATK support. It's good enough to provide 320 a basic user experience with Accerciser now, but we'll keep 321 improving it in further releases. 322 - New printing API that allows applications to control and monitor 323 the printing process, when requested by javascript or started by 324 the user. 325 - Many bugfixes. 326 327 ================ 328 WebKitGTK+ 1.1.4 329 ================ 330 331 What's new in WebKitGTK+ 1.1.4? 332 333 - WebKitWebView gained uri and title properties, deprecating the 334 usage of the title-changed signal. 335 - Basic functionality for HTML5 media tags has been achieved; there 336 are many unimplented methods, and rough edges still, though. 337 - Font rendering received quite some love, with layouting, and 338 memory handling fixes, and at least one less crash. 339 - A new signal, new-window-policy-decision-requested, has been added 340 to WebKitWebView, that makes it possible for the application to 341 correctly decide what to do when new windows are requested. 342 - A bug that made tooltips for consecutive links not update their 343 location was fixed. 344 - Several improvements were made to the HTTP backend, including 345 making it more robust when talking to servers which send bad 346 Content-Type headers. 347 - WebKitWebView now uses the GtkBinding system to handle key events, 348 which means that the user is now able to customize the keys used 349 for various operations, and that many subtle bugs have been fixed. 350 351 ================ 352 WebKitGTK+ 1.1.3 353 ================ 354 355 The 1.1.3 release was just a quick bug fix release, because we made a 356 mistake in library versioning. 357 358 ================ 359 WebKitGTK+ 1.1.2 360 ================ 361 362 What's new in WebKitGTK+ 1.1.2? 363 364 - Added support for downloads: a new signal, 'download-requested', 365 will be emitted by WebKit when a dowload is requested. On top of 366 that, the download process has been encapsulated in a new object, 367 WebKitDownload, which allows the user to control it or to start 368 new downloads from the client side. 369 - Added webkit_web_view_get_encoding to get the automatic encoding 370 of the current page. 371 - Added GObject properties for 'encoding' and 'custom-encoding'. 372 - Added 'javascript-profiling-enabled' property to the WebInspector, 373 which allows to enable and disable the profiling functionality. 374 - Added API to create and add history items to WebKit's history. 375 - Improved debugging support with WEBKIT_DEBUG environment 376 variable. Most of the settings will only give useful output for 377 debug builds, but WEBKIT_DEBUG=Network will log all HTTP traffic 378 form libsoup to console. See WebCore/platform/gtk/LoggingGtk.cpp 379 for all the options available. 380 - Lots of bugfixes. 381 382 ================ 383 WebKitGTK+ 1.1.1 384 ================ 385 386 What's new in WebKitGTK+ 1.1.1? 387 388 - ABI compatibility with 1.0.3 was broken, so you will need to 389 recompile your application against 1.1.1 390 - Support for the CURL backend was dropped, libsoup is the only HTTP 391 backend now. 392 - webkit_get_default_session, to get the SoupSession used internally 393 by WebKit. 394 - 'create-web-view' signal, emitted when the creation of a new 395 window is requested. 396 - 'navigation-policy-decision-requested' signal, emitted when a 397 navigation to another page is requested. 398 - 'mime-type-policy-decision-requested' signal, emitted each time 399 WebKit is about to show a URI with a given MIME type. 400 - Support for the Web Inspector 401 (see http://webkit.org/blog/197/web-inspector-redesign/) 402 - HTTP authentication support, with optional gnome-keyring storage. 403 - New load functions: webkit_web_view_open, webkit_web_view_load_uri 404 and webkit_web_view_load_request. The old 405 webkit_web_view_load_string and webkit_web_view_load_html_string 406 are now deprecated. 407 - webkit_web_view_reload_bypass_cache 408 - webkit_web_view_{get,set}_custom_encoding, to override the 409 encoding of the current page. 410 - Improved stability and lots of bugfixes. 411 412
