Summary: | Start Plugin button does not appear (initially) | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Grósz Dániel <groszdanielpub> |
Component: | nsplugins | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | adawit, aiacovitti, jsardid |
Priority: | NOR | ||
Version: | 4.10.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Grósz Dániel
2013-10-12 17:42:36 UTC
It happens with other types of embedded files (such as text or pdf) too. In that case the behavior is the same with Webkit and KHTML. I can confirm this happening sometimes for flash based plugins, but not for other embedded kparts. I also confirm the bug. I actually wonder why this bug is not receiving attention, as it is very reproducible and quite annoying. Perhaps it is that few developers currently use konqueror (or rekonq) nowadays, or that they load flash content directly (weird) or not at all... Could you post an example of page affected by this issue? This is just an example I can recall now: http://www.ara.cat/arabassas/LEditorial-Antoni-Bassas-Vuit-dramatiques_3_1309699022.html I will try to find others... Thanks I think I can refine where the actual problem is. The issue is not there anymore when a web page tries to directly load a flash video (this has been properly fixed, as far as I can see), but persists if the flash video needs to be manually activated with a play button (such as in the example above). In that case, clicking in the play button creates a black video frame and the start plugin is missing, which is confusing for the final user. Only if one reshapes the window, the start plugin button appears. I would propose two ways of solving this issue, although I don't know which one is easier to implement: - for the cases that a play button exist, there is actually no need for the start plugin, so it could be disabled for those cases. - if previous point is difficult to implement, could it be easier to trigger the start plugin button right after manually clicking the play button? (In reply to Andrea Iacovitti from comment #4) > Could you post an example of page affected by this issue? Any page with flash for me. (In reply to avlas from comment #6) > - if previous point is difficult to implement, could it be easier to trigger > the start plugin button right after manually clicking the play button? I'm pretty sure that's the intended behavior; that it doesn't happen is a bug that should be fixed. Git commit abdf2417cfefc360c78696485842a131a1cff048 by Andrea Iacovitti. Committed on 26/02/2015 at 14:44. Pushed by aiacovitti into branch 'Applications/14.12'. Use default color palette for "Start Plugin" button to ensure its visibility. M +4 -3 nsplugins/nspluginloader.cpp http://commits.kde.org/kde-baseapps/abdf2417cfefc360c78696485842a131a1cff048 Is this a problem of visibility only? If that would be the case clicking on the invisible button (at the center of the video fram) should work but that doesn't seem to be the case... But perhaps I'm missing something (In reply to avlas from comment #9) > > Is this a problem of visibility only? As i understand it, this is the problem this bug report was opened for. The other issue you mentioned in previous comment has nothing to do with this ticked and probably is already tracked by bug 246736 (haven't go in deep to tell for sure). If you read the comments, in particular the first one, it points to something that is not about the color in which the button Start Plugin appears, but to the fact that the button does not appear (exist) until you resize the window. So I would say you fixed a bug that is not what the intention of this bug was about (although the title may be confusing and the bug may certainly be a duplicate of the bug you mentioned). Am I wrong? It doesn't work for me either if I click where the button is supposed to be when it's not visible. For whatever reason, now the bug doesn't manifest for me with youtube, whether on the site or embedded. (A few days ago it still happened. Maybe an update?) But the bug still happens on other sites with flash. (In reply to avlas from comment #11) > > If you read the comments, in particular the first one, it points to > something that is not about the color in which the button Start Plugin > appears, but to the fact that the button does not appear (exist) until you > resize the window. So I would say you fixed a bug that is not what the > intention of this bug was about (although the title may be confusing and the > bug may certainly be a duplicate of the bug you mentioned). > > Am I wrong? Second line of comment 0 "If I use KHTML, the button never appears ...". The fix address nspluginviewer that is only used by KHTML and not Webkit rendering engine and, at least for me, it makes the "Start Plugin" button clearly visible for youtube flash content (previously was rendered with transparent color, thus invisible). (In reply to Grósz Dániel from comment #12) > It doesn't work for me either if I click where the button is supposed to be > when it's not visible. > > For whatever reason, now the bug doesn't manifest for me with youtube, > whether on the site or embedded. (A few days ago it still happened. Maybe an > update?) But the bug still happens on other sites with flash. Could you please clarify which "other sites with flash" are you referring to by posting url and/or a screenshot? Thank you. Oh, I see. You fixed the part of the bug report specifically related to the invisibility under KHTML rendering... (I didn't realize of this, as I use Webkit) > Could you please clarify which "other sites with flash" are you referring to > by posting url and/or a screenshot? > Thank you. Youtube and dailymotion are fine. Examples I found with the bug: http://index.hu/video/2015/02/24/budacash/ http://www.timesofisrael.com/false-israel-drowns-gaza-claims-sweep-internet/ (This one should load after clicking on it, but the index.hu one should load immediately.) Dear user, KHTML (and KJS and all related Java/plugin infrastructure) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann |