Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
07-20-2012 02:14 AM
I noticed some new behaviors in the new WebKit rendering engine. It's not limited to one (of the two) browsers, but also occurs in WebWorks apps:
1.) Selecting elements that use the onclick handler or have some other type of event handler bound to them, get a black (or white) border painted around it as soon as you touch them - even if just for scrolling the page. Bug or feature (for keyboard devices)?
But if that wasn't bad enough, this border does not get scrolled when the element is. See screenshots:
Using the following CSS definitions did not help:
-webkit-user-select: none; -webkit-tap-highlight-color:rgba(0,0,0,0);
2.) Context menu. According to the blog post this is something we currently have to live with. Altough the new selector in general is pretty cool, I need to way to disable this context menu in an easy way.
Solved! Go to Solution.
07-23-2012 11:46 AM
Thanks for reporting this.
Can you provide a sample that reproduces the border rendering issue (using http://jsfiddle.net/)? I'd like to use this exact code sample to escalate this issue internally for investigation.
For your request about context menu, I have passed this feedback along to the product management for review I recall the WebWorks SDK for Tablet OS added specific instructions to the compiled BAR file to disable the context menu. However, on BB10 the context menu is a bit more important (in terms of allowing your app to connect & flow with the OS). However I see your point about the need to disable it should that better reflect the user experience you want in your app.
07-23-2012 12:17 PM - edited 07-23-2012 12:21 PM
I did a super-minified version of one of my problematic scrolling pages. It will throw dozens of errors since I didn't include images or JS functions. Those are not necessary to show the ugly black/white borders.
It was more or less done by copying my app's output (using Webinspector) and by manually copying some CSS attributes...
Here are the links:
Preview on device: http://fiddle.jshell.net/UABLu/2/show/light/
<edit>I've attached two screenshots.</edit>
07-24-2012 09:29 AM
I've submitted a defect for this issue to the browser team for review:
09-02-2012 04:06 AM
Still under investigation.
I've still submitted a first beta of Campus-App for BB10 for review. Perhaps just to show off this and the font rendering issue. ^^