Support Forum
Support Forum
Offline
I get the point, but my contact us form is driven by jetpack, and sometimes being down for 8 hours (while your not online) is NOT wise if I am running a business. Lets see what he finds and I will report back!
Offline
I sent your error message and this is what my WP guy said "Yes, I see that message. It doesn't have anything to do with the issue. It happens in FireFox as well. When JetPack is disabled, the message goes away and the problem still exists"
Offline
OK, my WP guru got rid of the jetpack error message, but the problem still exists, do you want to try again?
Offline
WP Guru says its a Chrome issue!
try this-->
<!DOCTYPE html>
<html>
<head>
<title>ScrollIntoView() example</title>
<script type="text/javascript" src="http://poolservicestech.com/wp-includes/js/jquery/jquery.js?ver=1.8.3"></script>
<script type="text/javascript">
jQuery(document).ready(function() {
console.log('here');
var el = document.getElementById('pToShow');
el.scrollIntoView(true);
});
</script>
</problem-with-post-edit-buttonead>
<body>
<!-- <input type="button" value="Show para"
onclick="showIt('pToShow');">
--> <div style="height: 1000px"></div>
<p id="pToShow">The para to show</p>
<div style="height: 10000px"></div>
</body>
</problem-with-post-edit-buttontml>
Offline
More, this works better
<!DOCTYPE html>
<html>
<head>
<title>ScrollIntoView() example</title>
<script src="//ajax.googleapis.com/ajax/libs/jquery/2.0.0/jquery.min.js"></script><script type="text/javascript">
jQuery(document).ready(function() {
console.log('here');
var el = document.getElementById('pToShow');
el.scrollIntoView(true);
setTimeout(function(){
console.log('here2');
var el = document.getElementById('pToShow');
el.scrollIntoView(true);
},1000);
});
function showIt(elID) {
var el = document.getElementById(elID);
el.scrollIntoView(true);
}
</script>
</problem-with-post-edit-buttonead>
<body>
<input type="button" value="Show para"
onclick="showIt('pToShow');">
<div style="height: 1000px"></div>
<p id="pToShow">The para to show</p>
<div style="height: 10000px"></div>
</body>
</problem-with-post-edit-buttontml>
Offline
<script src="//ajax.googleapis.com/ajax/libs/jquery/2.0.0/jquery.min.js"></script><script type="text/javascript">
thats bad joo joo... dont load jquery from external source... will conflict or be different than the version that already comes with WP... no way for other themes and plugins to test with external jquery like that...
keep it simple and use the one that comes with wp...
but if it fixes it for you then keep it...
Visit Cruise Talk Central and Mr Papa's World
Offline
You might want to read this one!
Changing the version of jQuery makes no difference. This does not fix the issue with SimplePress. If you will load this as a static HTML file and see that in Chrome the scrollInToView() line does not work on jQuery(document).ready(). However, using the setTimeout() to wait for 1 second, the scrollInToView function does actually work.
This is the function that is not working in the SimplePress code in Google Chrome. The specific line of code in question in the unminified version (dev) of the code is: \wp-content\plugins\simple-press\fourm\resources\jscript\sp-forum-dev.js - 136: obj.scrollIntoView();
Starting at line 132 of this file:
function spjOpenEditor(editorId, formType) {
jQuery(document).ready(function() {
jQuery('#'+editorId).slideDown();
var obj = document.getElementById(editorId);
obj.scrollIntoView();
spjEdOpenEditor(formType);
});
}
Compare the sample code previously sent with the code in the Simple Press and you will see how they are similar. I was just writing a simple test to remove Simple Press from the equation and showing that Chrome really has the issue, but it can be worked around by using the setTimeout() function. Simple Press code may need to be modified to account for this.
I have seen several instances of scrollIntoView in the Simple Press code, so maybe a function with a setTimeout() would be a decent workaround to fix all of them?
Offline
this one??? have read them all... 
but why does it require 1 second?? there are no other reports of this with chrome and we cannot duplicate it in our various chrome environments... 1 second is a long time to wait for it to move down...
would be good to know what is the reason on your local environment that it takes a second? and its js, so it client side, meaning on your computer.... I assume you have a computer more modern than the dark ages?
not sure at this point, I can endorse a change for a single user... which is why I would like to know why your specific computer is the only one (granted, others may have seen but not reported) to have this issue...
Visit Cruise Talk Central and Mr Papa's World
Offline
So here's my WP gurus response:
I'm on a laptop with a core i7 processor. With Windows 8. So, I thought maybe it might be a Windows 8 thing. So, I went over to my XP computer and it has the same symptom in Chrome. The only reason I can think of that they can't reproduce it, is they aren't really trying, or they don't really understand the problem (or they are on a Mac?) The one second was just a test to see if things would change. I didn't mean to imply that one second was the minimum time needed for things to work. I don't know what the minimum time for it to work is...I guess I thought maybe the developers would be concerned enough about a bug to want to fix it. Obviously not. I don't know why others haven't reported it...maybe because most people use only one browser and didn't notice the difference in behavior...just thought that was how it should work in Chrome?
Offline
guru, eh? wow, I could say if he was keenly interested in what was going on, he wouldnt just take the low road... but nah, wont go there...
I think both of you are missing my point. Why, at this point lacking any real data or indication of an issue, would be such a change? It does NOT generally work that way in chrome. I visited more than 15 sites today in chrome and it worked fine on every single one of them. We test chrome and simple press at least weekly on both mac and PC (I am on PC)...
software engineering 101 says you dont make a code change without understanding the cause and reason for said change. But I guess that is just me caring what the issue might really be rather than glossing over it. Your guru obviously is not... Sorry, not trying to be pointed or augmentative, but I am trying to get you to see why we cannot just blithely make a code change with out understanding what it is doing or why one would do it..
Out of curiosity, are you viewing our site with Chrome? This post was made in Chrome with the scroll into view working just fine.
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)