Bug 845090
Summary: | Default KDE browser is buggy and provides a terrible first user experience. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Torrie Fischer <tdfischer> |
Component: | kde-baseapps | Assignee: | Than Ngo <than> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | dennis, jreznik, kevin, ltinkl, rdieter, rnovacek, than |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-01 18:34:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Torrie Fischer
2012-08-01 18:13:48 UTC
Bugzilla is not an appropriate venue for this kind of change requests. And any concrete issues with Konqueror should be reported directly to bugs.kde.org. Where exactly do I send change requests then? I assume then that since this isn't a bug, it is expected behavior to be unable to download chrome on a fresh install of Fedora 17? > Where exactly do I send change requests then? The default applications are discussed in KDE SIG meetings. That said, the default browser topic has been rehashed many times and Konqueror was the decision for several practical reasons (it's dragged in by the KDE workspace, it's small, it's a KDE app and it's upstream KDE's default browser), so I'm not convinced rehashing this issue is productive. Please keep in mind that the choice of defaults is a highly subjective matter and you cannot make everyone happy. (You have to sometimes make unpopular decisions in Phonon as well. And look at how you have 2 different backends because people cannot agree on which is the "best".) > I assume then that since this isn't a bug, it is expected behavior to be unable > to download chrome on a fresh install of Fedora 17? That's a KHTML bug (or missing feature, depending on what exactly the JavaScript on that site is trying to do), I'm sure the upstream KHTML developers would be happy to hear about it (and that way there's some chance the issue can be fixed in F17 updates, whereas default applications for F17 CANNOT be changed anymore, the defaults discussion would be for F18 at the earliest). Thanks for having filed the upstream bug report (kde#304392). |