What does the question mark mean on MDN browser compatibility table?
A question mark on compatibility table means anyone did not filled the
the browser's support for the feature yet.
Simply it means "Unknown".
Check this contribution guide from MDN.
https://developer.mozilla.org/en-US/docs/MDN/Contribute/Structures/Compatibility_tables
Related
The element has ARIA role="treegrid" despite it functionally being an element that should have the ARIA role="grid". Go to the Vaadin Grid component page and inspect the first table in the Accessibility tab. It has role="treegrid".
From my understanding, this is the wrong role, because the rows can not be expanded in this Component.
See treegrid role on MDN.
The correct role should be "grid", just like the name of the Component.
See MDN grid role
Am I understanding this correctly? Shouldn't the role be grid?
Note: I am an accessibility tester with no access to the source code, I found this using dev tools while inspecting my colleagues work and the Vaadin docs. This means I do not know if this is an error in the documentation and my colleagues just made the exact same error or if this is a bug in the framework.
Good catch, and yes, you are understanding this correctly.
To cite the related bug report:
...it may prove to be confusing to screen reader users. While they will never be able to expand the tree that contains only 1 level of data, they will still hear "Level one" announced which is suggestive of there being more levels. Without being able to see the table, it is not unlikely that a screen reader user would assume that there is more content that they cannot access but without know why. It's not the biggest problem, but it adds an element of uncertainty.
What to do if you discover an error like this
1. check if the issue is known
In Open Source libraries like Vaadin, you can go to their issue tracker and search if the issue is known. Often, these are GitHub or Gitlab pages, and you usually find a link on the library’s public page in the header or the footer.
For example, this is an issue already known by their developers: Grid uses treegrid role even when populated with only 1 level of data #4318
As you can see, these components often are able to cover much more complex scenarios, so the Grid component is capable of becoming a real tree grid, but in the configuration used in your project it’s not.
2. Create a bug report if it’s not known yet
If you cannot find anything, go ahead and file a bug report.
Usually, you’d also find some guidelines on how to do that.
3. Fix the issue in code
As I find myself repeatedly pointing out recently: There is no point in trying to fix accessibility issues from the outside of a library. It’s often a hack, therefore fragile, inefficient, and only your project profits from it.
Instead, if you have developing force, go and fix the issue at the source, if it is important to your project. This is how Open Source works in a nutshell: Somebody, for whom the issue is critical, provides a fix for everyone.
For example, the Vaadin Contribution Guide explains how to go about this.
just like what the title says
I couldn't find a single detailed explanation with this vulnerabilities
any comments is appreciated
see link for more info
https://cordova.apache.org/announcements/2016/04/27/security.html
The NVD is a product of the NIST Computer Security Division and is sponsored by the Department of Homeland Security's National Cyber Security Division. This is the official resource to see more information about announced vulnerabilities:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5207
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5208
You could investigate this further by analyzing the Cordova iOS source on GitHub and history of commits:
https://github.com/apache/cordova-ios
The CVE sometimes is not incredibly descriptive on how the bug actually works because they're trying to thwart less-skilled hackers from easily writing exploits for the bug immediately after it's released. Oftentimes you will have to investigate the source code to see what changes were made yourself to recreate the problem.
Where can I find the documentation for IdocScript for Stellent/Oracle UCM? I just got assigned to do maintenance on a page that uses it, and have no prior experience with either Stellent or the script. My specific problem has to do with string manipulation, but I can hardly find any documentation online at all, odd for a programming-related topic.
If you are after a book, there is the one by Brian Huff (Bex - http://bexhuff.com/) linked below.
Actually it is the only one. Written before Oracle bought Stellent and may be a missing some IDOC changes.
As a resourse tho it is very handy to have around as it touches on all things UCM (including a decent chunk on IDOC).
The Definitive Guide to Stellent Content Server Development
~ Brian Huff
Of course I answered my own question 15 minutes after I asked it. Oracle has a guide buried deep in its documentation website. It's available as a PDF or in HTML format (thanks, Raystorm).
We've started using TFS at work, and I'm migrating my bugs from the previous issue tracking software to TFS. All of them are written in Hebrew, a right-to-left language, but mixed with English words.
All the text fields in the TFS client are left-to-right, so I have to manually go and press Ctrl-Right-Shift in all the fields in order to read them properly.
Is there any way to change the default text orientation in TFS client?
I looked into customizing the work item form elements, for example here:
http://msdn.microsoft.com/en-us/library/ms194963.aspx
but I couldn't find any attribute for changing the text orientation.
As far as I understand it there is not a way of changing the text orientation in the work item definition. I've passed your question along to some guys on the team in Microsoft to see if they know of anything.
is there an answer? Since then I continued searching for a way to do this, but I couldn't find any.
This is a serious usability issue for me, especially with the titles, which have mixed Hebrew-English. When displaying the issue titles I have to read "backwards". When scanning a lot of issues, this is a serious pain.
And I do not have the spare time to translate 500+ issues from Hebrew to English.
Please down vote me if this is not appropriate, but I'm desperate to the point of pulling my hair out looking for this link. This is really a last resort.
Recently I browsed to a blog (at least I think it was) that had a very detailed description on how to modify a TListBox to have a multi-line look resembling some of the entries on an outlook list of emails, with a Title and the initial content. It was a particular good example because it had all the code for the modified TItem and TItemList objects and loads of images with that look
I've scoured my Firefox History, my Chrome history, my FeedDemon Feeds and my Google Bookmarks to no avail. I've done Google searches with TListBox, TListView, TItems, TItemList, Custom, Extending and some other variations and even looked 3 page results down to no avail...
Has anyone stumbled upon this article?
Please let an "old" man recover his memory, and his sanity :)
Cheers,
Gus
How to use is the one that "TListbox Ownerdraw Delphi" finds for me. Certainly Ownerdraw is what you are looking at to do this sort of thing. Good luck!
To answer my question with a proper answer:
Blaise Pascal Magazine Issue 4 November 2008 page 27.