Version: KDE 2 to KDE 3.1.x, inclusive (using KDE KDE 3.1.1) Installed from: SuSE RPMs OS: Linux Thanks to Archive Webpage grabbing focus for EVERY DAMN ELEMENT of a page, even if there are hundreds of images involved, one is Denial Of Service'd from one's system until it is done. Period. This had been reported as slightly affecting browsing ( suggestion/wish/bug #29284, IIRC ), but it doesn't only affect browsing. I cannot type-into a text-editor while this is going-on, because any-time I hit the space-bar I've probably just cancelled some piece of the archiving. Also, with focus being GRABBED every second, for however many minutes it takes to archive the page, it simply renders the ENTIRE system non-usable. ( even dual-head with me working on the other desktop ) TWO minutes DoS for archiving http://www.theregister.co.uk/content/53/31665.html for me. FIVE MINUTES AND 25 SECONDS DoS for archiving http://www.abit.com.tw/abitweb/webjsp/english/pt_main_back.jsp?pPRODUCT_TYPE=MotherBoard&pMODEL_NAME=KV7 Can't *useless* windows, like the Grabbing A Little Component Of Something .. be NON-focussed on instantiation, and Z=behind, somewhat, the Currently Focussed Window? AND can't single-window-for-downloading/archiving be implimented to PERMIT us to have our own system's function? That second bit, there, is important, actually, as it currently IS NOT possible to cancel the archiving /itself/ by any means: one may only cancel each element of the archiving, and hope that one gets through all the cancellings intact, relatively soon... microsofting us again... Mozilla doesn't DoS us while archiving a page ( at least not that *I* remember, but I prefer the atomic .war format to Mozilla's strewn-everywhere format )... Please correct this, we've been controlled beneath this, since KDE 2 ( IIRC, coulda been 2.2. or 1.x.. ) and didn't understand why this microsofting of us continued, and it just dawned on me, recently, that the konq developers ( probably ) simply don't archive enough pages to have hit it as a 'problem', is all... Some distant sites take more-than-five minutes, by a large margin, though thankfully I don't try such often...
PLEASE delete 61055 and 61056, as I only hit COMMIT once, yet all three versions got databased!? I'd assumed that COMMIT would have the same meaning here as it does on slashdot, and that one could preview one's comment before committing, hence the actually /having/ of a 'commit' button. Perhaps I should put *this* as a bugzilla UI bug?? Whatever, kill my 2 previous reports, please, and thanks
.
hmm.. works fine for me in HEAD, but those pages seemed to be archived in about ten secs.
If the version /you're/ using grabs copies of the page-elements from the in-memory copy of the page, then 10s would be all it'd take every time, but the production version of it, SuSE's KDE 3.1.1, in this case, ignores the in-memory copy and grabs every element, one at a time, from the 'net. Also, if your ISP's caching everything with a proxy, that'd change the rules, too. I think..
My kde version always attempts to connect, i don't know if its to check the updateness of the pages or page elements or download, but it sure takes a long time, and i want this fixed. I archive a lot of web content and this turns web archiving useless.
maybe this is a duplicate of bug # 59965
Replaced marvin@synapse.net with cshobe@osss.net due to bounces by reporter
Works for me with KDE 3.2.3. The dialog does not grab focus and pressing "cancel" cancels the entire archiving. So if you still experience this write down steps on how to reproduce, please. If nobody experiences this bug any longer it will be closed.
*** Bug has been marked as fixed ***.