New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed DHTMLControls #1116
Fixed DHTMLControls #1116
Conversation
A+ commit 👍+10 edit: Actually, after playing around with this in normal use scenarios, the history buttons seem quite glitchy to me. Have you tried this out? |
Works fine for me. In what case is it glitchy for you? |
Alright, so there aren't the bugs I'd thought I'd found.
|
Doesn't happen for me.
I didn't touch this but I agree that it's retarded so I'll add a commit for that. |
There is a history corruption issue with fragment identifiers (the @willox Can we get |
Added now. |
dce36d7
to
236dd75
Compare
236dd75
to
0ee48da
Compare
This will need to be updated for http://wiki.garrysmod.com/page/Panel/StopLoading for the next update. |
Done. |
@zerfgog The merging of the stop and refresh buttons unfortunately won't happen (and thus is reverted) since apparently some addons relied on the internal view hierarchy of DHTMLControls for some reason and broke when the buttons were merged. |
@Bo98 😐 that's quite unfortunate |
Put a warning out next update, deprecate the behaviour, merge your PR |
This control is eventually going to be deprecated and replaced in its entirety when CEF is implemented so we can wait until then and make sure the changes are there for the new control. At least the critical bug fixes are merged - it was only the button merging part that was reverted. |
After the Awesomium functions and hooks now work/exist, this control can now be fixed. It was pretty much broken at everything except entering URLs into it.
Side notes about the reasoning behind some of the changes:
self.Refreshing
was replaced with a URL check as such check was required to prevent a double history insertion on setup. If the controls were hooked before the initial page began loading (likely scenario as:OpenURL(...)
doesn't start loading immediately) then the history would be appended on setup and again on load. Instead of removing the initial insertion, a history check was added in case someone decided to add the controls later. This also covers refreshes so that special boolean isn't required now.self.NavStack
was useless and is now removed.