PWaddict

Members
  • Content count

    293
  • Joined

  • Last visited

Community Reputation

97 Excellent

About PWaddict

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,158 profile views
  1. I just found this one http://www.malevole.com/mv/misc/text/
  2. @maxf5 Did you installed the Page Path History core module?
  3. I'm already having the latest graphics driver. I don't think that's possible to roll back to an older version of Chrome but I've just installed the latest beta version of Chrome 62.0.3202.45 and the issue is gone. Btw the images are blurry on the beta so I will uninstall it and wait for an update on the stable version. At least now I know that they fixed it. I will post again on the next stable version.
  4. I've already disable all the extensions and the issue is still there. I tried both and the issue is still there.
  5. I've already updated to the latest nvidia drivers 385.69. I always have the hardware acceleration disabled. I forced vsync on Chrome but nothing is fixing the issue.
  6. Install the Admin Custom Files module. On site/templates/AdminCustomFiles folder create a css file named ProcessPageEdit.css and add the following code: .InputfieldImageButtonCrop { display: none !important; } Then on the Admin Custom Files module settings at the "Activate for process" section select ProcessPageEdit, (Page Edit).
  7. While I was developing a website in the previous week I notice a strange behavior on Chrome browser. When hovering on image links they were moving down 1px and sometimes getting vertical screen tearing. I couldn't find why this was happening. I googled about this issue and didn't find something similar. Then I saw the exact same issue on other sites too (not mine). It doesn't always happen, you have to scroll up/down first and try to hover on links or img links or even click on those links. I tried other browsers like Firefox, IE11 even the Steam web browser and everything is working fine there. In the previous week Chrome updated to 61.0.3163.100. Is any of you having this issue? Here is screenshot while I was hovering the navigation menu on the Steam site and the vertical screen tearing happened.
  8. @renobird Are you trying this on localhost or server? You should try both with the same installation.
  9. To always display the map at the center even if the browser resized or the full screen button pressed just use the below function: google.maps.event.addDomListener(window, 'resize', function() { var center = map.getCenter() google.maps.event.trigger(map, "resize") map.setCenter(center) });
  10. Here is my best solution so far. Now, when I click on the "a:not(.external)" links the pages are always load with "scrollTop(0)" and when I use the browser's back/forward buttons "popstate" I always get the saved scroll position. There is only 1 tiny problem with the "popstate". Once I press the browser's back/forward buttons I get instantly the saved scroll position on the current page and then the page gets replaced with the correct one. How can I make it to get the scroll position ONLY when the page gets replaced and not before? $(function() { $(document).on('click', 'a:not(.external)', function(e) { var replacePage = function(url) { $.ajax({ url: url, type: 'get', dataType: 'html', success: function(data) { $(window).scrollTop(0); var dom = $(data); var title = dom.filter('title').text(); var html = dom.filter('.ajax-container').html(); $('title').text(title); $('.ajax-container').html(html); } }); }; history.pushState(null, null, this.href); replacePage(this.href); e.preventDefault(); }); $(window).on('popstate', function() { var replacePagePopstate = function(url) { $.ajax({ url: url, type: 'get', dataType: 'html', success: function(data) { var dom = $(data); var title = dom.filter('title').text(); var html = dom.filter('.ajax-container').html(); $('title').text(title); $('.ajax-container').html(html); } }); }; replacePagePopstate(location.pathname); }); });
  11. @abdus It doesn't work and I don't know how to modify it but thanks anyway!
  12. bump
  13. There is only a small "downside" if the website is already online. All links from the default language (except homepage) will change so the Page Path History module MUST be installed to avoid 404 errors from previously shared pages, google search etc. Make sure to update your README.md with all these important info.
  14. @Mike Rockett nice "trick"! I don't remember seeing that option on LanguageSupportPageNames. I will definitely gonna use that. I'm currently using the language_iso_code field not only on my sitemap but also on site's navigation (hreflang) and the flag icons but I will delete it
  15. I'm currently using the Window Resizer Chrome extension.