Kari Ikonen

Tried out experimental patch, which in my use case works fine (since "total time of whole request including transfer time" is good enough factor for in my use specific case;...

In my case access is into internal private REST API, and if there's access problem then it most certainly occurs in initial connection. Also logic (in my case) works so...

Any news or workarounds on this. I.e. I just got stuck with problem of needing to run local docker container, which needs to access services in kubernetes. okey, kubefwd nicely...

Quickly testing this might be "good enough" workaround for my needs for a while. *EDIT* Nope, it does not work, since it plays havoc with docker DNS logic between containers...

Another workaround attempt via using tips from https://stackoverflow.com/questions/17770902/forward-host-port-to-docker-container worked fine.

For project where I need it, this lost focus poses nasty usability problem, since accessibility is broken.

Related: #5626

It looks like this monkey patch fixes it ```ruby module PryByebug module Helpers module Breakpoints def text Pry::Helpers::Text end end end end ```

The thing is that "keyboard accessibility" is mandatory requirement in various places, just due to legalize rrequirements (like ADA in USA).

I will try to look into it