http://blog.gmane.org/gmane.os.opendarwin.webkit.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24914 <pre>Hello. In WebGLRenderingContext::setupFlags() there is a line: m_isGLES2NPOTStrict = !m_context-&gt;getExtensions()-&gt;isEnabled("GL_OES_texture_npot"); My question is: why is this negation? Now NPOT textures doesn't work in WebKit but without this negation NPOT textures works fine. Is this disabling of NPOT textures intentionally? Thanks for reply, Przemek _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> SzymanskiPrzemyslaw 2013-05-23T07:14:31 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24913 <pre>And there is an overwhelming evidence: http://trac.webkit.org/changeset?reponame=&amp;new=150559%40trunk%2FLayoutTests%2Fplatform%2Fmac%2FTestExpectations&amp;old=150476%40trunk%2FLayoutTests%2Fplatform%2Fmac%2FTestExpectations - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Ryosuke Niwa 2013-05-23T01:11:28 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24910 <pre>Hey all, I've read the document at http://www.webkit.org/coding/RefPtr.html, but I still have some questions about using RefPtrs. The first one is listed in the "Improving this document" section of the aforementioned documentation: • Perils of programming with TreeShared. What does that mean? What gotchas should I be aware of? (Heck, more details on any of the things in "improving this document" would be helpful, and I'll do my best to update the document with anything I learn if that's desired.) Also, I've noticed that there's both TreeShared and RefCounted, and they seem fairly similar to my uninitiated eye. What's the difference between the two and when should one use one or the other? Also, are there other templates/classes that I should be aware of? Thanks, Bem </pre> Bem Jones-Bey 2013-05-22T16:26:34 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24898 <pre>Hi all, Following the discussion in the contributors meeting about layering violations I was thinking about moving all the accessibility stuff inside WebCore/accessibility into a new WebCore/platform/accessibility directory. My reasoning behind this could be summarized as this: * Accessibility code is actually already platform dependant, as every port supporting this exposes the accessibility hierarchy in slightly different ways (ATK flattens more the hierarchy than Mac, for instance). * Besides the AccessibilityObject wrappers and partial platform-specific implementation files (e.g. AccessibilityObjectMac.mm) present in places like WebCore/accessibility/[atk|mac], there are other bits in WebCore/accessibility that are platform specific as well (e.g. AccessibilityRenderObject). These bits are guarded with "#if PLATFORM" macros, which would still be necessary to meet the different requirements of each port. * The number of ports adding support for accessibility is increasing, some of them sharing code al</pre> Mario Sanchez Prada 2013-05-21T14:34:28 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24892 <pre>Hi, We’ve added BlinkMergeCandidate keyword to Bugzilla to track any Blink changes we might want to merge. Please add this keyword when you’re filing a bug or posting a patch to merge a Blink change. - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Ryosuke Niwa 2013-05-21T04:06:07 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24891 <pre>Does anyone object to supporting the Page Visibility API unprefixed? https://bugs.webkit.org/show_bug.cgi?id=102340 Should we keep support for the prefixed version? Simon </pre> Simon Fraser 2013-05-21T01:28:19 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24890 <pre>I'd like to remove the #ifdef, and make the interpreter an unconditional part of JSC. It's sometimes hard to reason about the different execution engines if you can't assume that the interpreter and its basic data structures exist. Thanks, Geoff </pre> Geoffrey Garen 2013-05-20T23:37:33 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24889 <pre>Hello, is anyone building WebKit2 without ENABLE_PLUGIN_PROCESS set, running Netscape plug-ins in the web process? The reason I’m asking is that having two code paths complicates things and I’d like to remove the non-plug-in process code path. - Anders </pre> Anders Carlsson 2013-05-20T22:15:43 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24887 <pre>Memory leak detection is a recurrent topic on this mailing list [1-5] but at present there exists only support for the Mac leaks tool[6]. The de facto standard for memory checking and leak detection for Unix is Valgrind and the goal of this work is to launch the DRT under Valgrind to generate a xml file with details of leaks found, and then to parse this file and display this information. Failures should result in the filing of memory bugs and adding the error to the suppression file. Chromium has a fairly mature process[7] for this which can been taken as the starting point. This work is being tracked under https://bugs.webkit.org/show_bug.cgi?id=116317. This is a work in progress, but as a first attempt leak checking can be done using the existing run-webkit-tests script as follows: $ Tools/Scripts/run-webkit-tests --gtk --leak --wrapper="valgrind" LayoutTests/accessibility/accessibility-node-memory-management.html The wrapper argument is used as a workaround because the the existing hooks</pre> Brian Holt 2013-05-20T14:48:51 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24884 <pre>Is any port interested in using ENABLE_INPUT_MULTIPLE_FIELDS_UI and/or ENABLE_CALENDAR_PICKER ? Don't you know what they are? Please look at [1]. These flags provide date/time input controls like desktop Google Chrome. These flags were enabled only in Chromium port, and they are dead code in WebKit for now. If no port has a plan to use them, we had better remove them. [1] http://trac.webkit.org/wiki/EnableFormFeatures </pre> TAMURA, Kent 2013-05-19T21:15:30 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24883 <pre>Hi everyone, I was looking at the PagePopup code and it seems to be BlackBerry specific. Furthermore, it seems to only be called from inside BlackBerry WebKit. Would it be possible to just move the code into WebKit/blackberry instead? I think someone with access to a BlackBerry build environment could do it in ~30 minutes or so. Thanks, - Anders </pre> Anders Carlsson 2013-05-19T18:36:21 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24882 <pre>Every time I look at TestExpectations, I find few dozen entries with # NeedsRebaseline. e.g. http://trac.webkit.org/changeset/150290 (there are still a ton left after this changeset) Please stop reducing our test coverage. Reviewers, please don’t r+ these patches. The ratio of people who end up not following up with their promise to rebaseline tests is way too high. - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Ryosuke Niwa 2013-05-17T19:58:23 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24877 <pre>The openBossa team at INdT Brazil is proud to announce “Nix” - a new WebKit2 port based on POSIX and OpenGL. Nix stands for “WebKit for unix-like platforms” and, if you consider the German meaning of the word "nix", it can be taken as “WebKit plus nothing”. We are looking forward to upstreaming and maintaining this port. Below you will find a brief history about Nix, besides its main goals and motivation. :: A little bit of history :: The first of Nix basic ideas arose from a conversation between Kenneth Rohde Christiansen and Noam Rosenthal, who were wondering about the idea of having a “platform/glib” or platform/posix”. Other ports such as EFL, GTK and Qt would then be able to develop themselves on top of it, having a common source core. While QtWebKit’s QQuickWebView is great for embedding web content into QtQuick, a few people felt they needed more freedom to implement a different WebView behavior than the one being provided by Qt. Behavior more suitable for tricky use cases lik</pre> Luciano Wolf 2013-05-17T12:41:27 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24874 <pre>Hi, CQ was stuck for the last 18 hours or so due to some test failures. I've fixed it but expect it to take another 4-5 hours to catch up. - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Ryosuke Niwa 2013-05-17T00:00:22 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24866 <pre>Hi, It appears that not a single port enables SHADOW_DOM build flag at this point, and WebKit doesn't even compile with that option enabled. (There are a few dozens of build failures). Is anyone intending to maintain the feature on trunk? If not, we should simply get rid of code behind this build flag for now; keeping unmaintained code that doesn't even compile isn't healthy for the project of our size. - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Ryosuke Niwa 2013-05-16T17:09:10 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24865 <pre>Hi there, I'd like to help get vertical selection support in textareas if possible. Is there anyone who might help point me in the right direction? If you haven't used vertical selection before, you can try it in Textmate, Sublime2, and many other editors by holding down the option key and dragging a selection. I think this would be helpful to have the browsers support natively especially as users are doing a lot richer editing in browsers nowadays. Cheers, Breck _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Breck Yunits 2013-05-16T16:49:15 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24861 <pre>Hi WebKit, I was wondering how folks debug memory errors such as use after free and allocated memory overflows. I have seen some bugs mentioning libgmalloc. I can run safari with: run-safari --debug --guard-malloc But I don't seem to get the full stack traces I have seen in the bugs. I have also seen mention of setting DYLD_INSERT_LIBRARIES to /usr/lib/libgmalloc.dylib, but doing so seems to lock up the build-webkit command. Any tips/tricks/pointers would be greatly appreciated, -Bear _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Bear Travis 2013-05-16T00:54:02 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24856 <pre>I'm trying to ascertain if, and when, Apple is planning on supporting the Web Speech API&lt;ttps://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html#tts-section&gt;. This email from Chris that was attached to this post&lt;https://lists.webkit.org/pipermail/webkit-dev/2013-January/023309.html&gt; earlier in the year, is the ONLY thing I can find on the web regarding Apple's support of the speech API, which is very surprising to me. Does anyone have any knowledge of whether or not Apple is planning to support this spec for Safari, specifically on mobile, and if so, when? Now that this is a W3C spec, and Chrome has added support for it, Apple is seriously missing the boat on this. As a developer of mobile optimized sites for large retail brands, we see speech to text as a game changer for the mobile web. Very interested to know if this is even on Apple's radar…and if not, why not? Thanks for any and all feed back on this topic. Randy _______________________________________________ webkit-dev mailing list webki</pre> Randy Brown 2013-05-15T23:46:21 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24850 <pre>Hello WebKit, There has already been some discussion about removing the CSS Variables code [1], and some early looks at what removing it from the code base would look like [2]. Currently, the EFL and GTK ports enable CSS Variables in the Source/cmake/Options[Efl/GTK].cmake files. I am proposing turning them off and excluding the CSS Variables tests until someone steps up to maintain the feature, or the feature is removed. I am proposing this as the cost of leaving the feature enabled is non-zero. The feature is incomplete and bugs are going to surface. Today I had a test regression with a css variables + exclusions test because the test and behavior were incorrectly implemented [3]. This regression turned up when it caused the bots to fail, and had to be diagnosed by today's gardener, and then forwarded to me to be fixed. I don't think this cost is worth it for a feature we are not (at least to my knowledge) planning to actively implement. -Bear [1] https://lists.webkit.org/pipermail/webkit-dev/2013-Apri</pre> Bear Travis 2013-05-13T22:36:39 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24833 <pre>Hi, I'm happy to announce that Christophe Dumez is now a WebKit reviewer. Chris has done great work on WebKit2 (test infrastructure, support for new device APIs) and one of the driving forces behind the EFL port. Lately he has been doing work on the Soup and GStreamer backends and the binding generators. Please join me in congratulating Chris ! Thanks, Laszlo _______________________________________________ webkit-dev mailing list webkit-dev&lt; at &gt;lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev </pre> Laszlo Gombos 2013-05-10T00:22:09 http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/24832 <pre>Hi WebKit, The CSS Exclusions &amp; Shapes [1] feature is currently behind a runtime flag that I would like to enable by default in the WebKit nightlies. The feature work is currently being done by myself, Hans Muller, Bem Jones-Bey, and Zoltan Horvath. We are tracking the work under master bug 89256 [2]. The current implementation focuses on shape-inside [3] and shape-outside on floats [4]. I also wanted to ask if there is a preferred method for accomplishing this. The most straightforward solution would be to set the runtime enabled feature to true by default in WebCore's RuntimeEnabledFeatures.cpp. An alternative approach would be to set up a preference in WebKit2's WebPreferencesStore.h with a default true value, and wire up the necessary plumbing. Thoughts? -Bear [1] http://dev.w3.org/csswg/css-exclusions/ [2] https://bugs.webkit.org/show_bug.cgi?id=89256 [3] http://dev.w3.org/csswg/css-exclusions/#shape-inside-property [4] http://dev.w3.org/csswg/css-exclusions/#shape-outside-property ________________</pre> Bear Travis 2013-05-10T00:21:50 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.opendarwin.webkit.devel