Comment #4 on issue 6001 by krtulmay: HTML tables should have a specific context-menu to allow opertions like sorting. http://code.google.com/p/chromium/issues/detail?id=6001
And I am also sorry to disagree with you on practically every point :-( > When chromium displays a textarea, it gives the user the ability to resize it Yeah, I know. And that is really BAD! > As sorting would be an optional feature, I do not see how it compromises the > integrity of the webpage. By allowing the webpage/table to be sorted/significantly changed/altered/manipulated differently, that in itself compromises the integrity of the webpage. > Well nothing prvents me from copying the data into Excel anyway. I do not see > how this is different That is different because you are copying the data somewhere else to do what you like with. Chrome/the browser is not automatically/arbitrarily making any changes to the webpage, which is the whole difference. > I would classify this in the same category as plugins such as SkypePlugin, that > turns phone numbers into links. I agree with your classification, which makes all such plugins borderline iffy. I probably draw the line at auto-linkifying text, where I have to assume the original text was not modified, but <a href=""></a> is wrapped around it. As well, a string of text is (hopefully!) the least innocuous, so that wrapping it with an href will hopefully not wreck the webpage. > We do have the inspector that allows changing the page content this doesn't seem > very different to me. Agreed. But that's because you are willfully making such changes yourself, and you are responsible for whatever results from those changes. And none of this even begins to touch where the temp storage for the table data will be stored and the fact that this would be all client-side. Use temp-disk space? Use RAM? What if the table is really large? What about really, really large? What defines a sorting order? Is it just collating order only? Can multiple languages be reliably detected, if at all? And I don't even want to think about all the DOM manipulation and Javascript being done now for Web 2.0. What if the original table row order is critical, but then it gets sorted? What if mouseovers, or checkbox checks, or dropdown changes, etc. perform row order dependent operations? What if there is even more complicated Javascript that might get triggered just on the sort? It's just too much of a nightmare to think about..... :-( -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
