<script>


function init(init_width){
 $("#exam_paper .exam_block").eq(0).show();
 check_ti_block(init_width);
}

function check_ti_block(init_width){
 $.each($(".ti_block"), function(key){
  block_width = Number($(this).css("width").slice(0,-2));
  left_width = Number($(this).children().eq(0).css("width").slice(0,-2))+init_width;
  right_width = block_width - left_width-10;
  
  $(this).children().eq(0).css("width", left_width);
  $(this).children().eq(1).css("width", right_width);
 });
}

$(function(){
 init(60);
});
</script>

이렇게 해도 안되시나요?

$(document).on('pageinit') vs $(document).ready()
The first thing you learn in jQuery is to call code inside the $(document).ready() function so everything will execute as soon as the DOM is loaded. However, in jQuery Mobile, Ajax is used to load the contents of each page into the DOM as you navigate. Because of this $(document).ready() will trigger before your first page is loaded and every code intended for page manipulation will be executed after a page refresh. This can be a very subtle bug. On some systems it may appear that it works fine, but on others it may cause erratic, difficult to repeat weirdness to occur.

Classic jQuery syntax:

$(document).ready(function() { 

});
To solve this problem (and trust me this is a problem) jQuery Mobile developers created page events. In a nutshell page events are events triggered in a particular point of page execution. One of those page events is a pageinit event and we can use it like this:

$(document).on('pageinit', function() {

});