Re: [Vimprobable-users] A bunch of issues and questions

[Karryanna <ka...@ka...>]

Hi Daniel,

thank you for all the time and effort you put into this!

> > • First of all, hinting sometimes doesn't work for me.
> > The only case I can report is search field at PHP website,
> > http://www.php.net
> > [...]
> 
> I can reproduce it, this is a bug. The hinting script does not know how to
> handle the <input type="search"/>. There are a lot of input types allowed
> through [html5][]. At the moment the input mode is started for input type
> 'text', 'password', 'checkbox' and 'radio' (by the way, makes it no sense to
> switch to input mode if a radion button is hinted).

OK, I'll hope for a fix then.

> > The other case I've noted down is webpage through which I sometimes submit
> > my homeworks, where hint for file selection shows but following it doesn't
> > really bring up the selection dialog. However, this site is login protected.
> > Anyway, I'd like to note that if I select next form field, tab back and
> > press enter, everything works as expected.
> > 
> > Is there any explanation to this, and more importantly, some kind of a fix?
> 
> That's hard to say without seeing the html code of the page.

Well, since it's login protected and tabbing back from next field is still
quiete comfortable, I'll let it be and only if I encounter this somewhere
else, I'll report it again.


> > • Searching terms with diacritics sometimes breaks the diacritics
> > Sometimes I try to search for a term including diacritics but when
> > I get results, it seems that the diacritics had been broken somewhere.
> > It should be reproducable for example here:
> > https://is.cuni.cz/studium/eng/kdojekdo/index.php?KEY=Az1
> > Say you wish to search for person whose family name is "Burešová".
> > After searching, I see "Burešová" in the field.
> > [...]
> > However, on many sites searching with diacritis works all right.
> > 
> > Do you have any ideas about what this could be caused by?
> 
> In general such issues are caused by different character encondings used for
> the page and the server side application.

Still other browsers can cope with that.
Is there a chance someone would get into that and possibly come with a patch
or workaround?
Or could someone give me a hint about how to find out more?


> > • Is it possible to download current page/file?
> > [...]
> 
> The was an path in the past that provided a :write or :save command to save
> the current opened document. But this was never merged into vimprobable, don't
> know why. A workaround could be the :print command that opens the print dialog
> where you can print the page into pdf or ps, but this isn't the same I know.

It's a pitty it wasn't merged. But thanks for mentioning, I'll try to search
the archive and see if I could apply it anyway.


> > • Is there any kind of hinting for frames?
> > I know that frames are evil and stuff but anyway, for example
> > http://srazy.hocz.org/index2.html
> > is a page informing about meetings of a community I belonged in and it's
> > made using frames. Is there a way to select the right frame so that for
> > example j/k movement takes effect? (It's not needed at real index but it
> > would come in handy after selecting some menu entry.)
> 
> This hinting does not exist, an we hope frame will fade away from the www. To
> implement the hinting wouldn't be too difficult, but the scrolling is done in
> vimprobable on a scrollable window containing the webview. I don't have any
> idea if there's a way to scroll within a defined frame without using
> JavaScript (like dwb does).

OK. I admit this is a kind of magic for me, I only remember that when I used
to use Mouseless browsing in Firefox several years ago, I could select a frame
and navigation in that frame then worked all right.
If it's not that easy at all, I can get over it somehow.


> Puh, that was a really long mail and it costs me a lot of time and attention.
> I think for the next time it's better to split the mail into single issue.
> These would be easier to answer and to keep track of unanswered issue and
> questions.

Sorry and once more thanks for the time you put in it.
You know, the idea of sending like ten mails at once felt so stupid. Now I see
it would had been better. Next time I'll split it. Or even better, I won't be
so afraid of the community and will report issues before there's so much of
them (though I guess it would be wise to wait for a few days and try to solve
them myself first).


Karry